diff --git a/locale/cs/LC_MESSAGES/admin-docs.po b/locale/cs/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..ac11ff7a --- /dev/null +++ b/locale/cs/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22092 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: 2023-07-29 15:18+0000\n" +"Last-Translator: Tomáš Kovařík \n" +"Language-Team: Czech \n" +"Language: cs\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n" +"X-Generator: Weblate 4.18.2\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "Chat" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "Jak vylepšit podporu přes chat?" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "Dobré zkušenosti" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "Získání podpory od člověka" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "Rychlá reakce na dotazy" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "Rychlé řešení mých problémů" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "Špatné zkušenosti" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "Dlouhé čekací fronty na psaní si s obsluhou" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "" + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +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 +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 "🙅 The following attributes are **not customizable**:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +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:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" + +#: ../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/clearbit.rst:9 +msgid "Avatar" +msgstr "" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/integrations/i-doit.rst:2 +msgid "i-doit" +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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +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." +msgstr "" + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "" + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +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." +msgstr "" diff --git a/locale/da/LC_MESSAGES/admin-docs.po b/locale/da/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..b6346622 --- /dev/null +++ b/locale/da/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22089 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: da\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "" + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +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 +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 "🙅 The following attributes are **not customizable**:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +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:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" + +#: ../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/clearbit.rst:9 +msgid "Avatar" +msgstr "" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/integrations/i-doit.rst:2 +msgid "i-doit" +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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +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." +msgstr "" + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "" + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" + +#: ../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/de/LC_MESSAGES/admin-docs.po b/locale/de/LC_MESSAGES/admin-docs.po index 26facecf..797f322a 100644 --- a/locale/de/LC_MESSAGES/admin-docs.po +++ b/locale/de/LC_MESSAGES/admin-docs.po @@ -7,17 +7,17 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-05-04 16:53+0200\n" -"PO-Revision-Date: 2023-05-23 09:17+0000\n" -"Last-Translator: \"JSX.RED\" \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: 2023-08-23 14:18+0000\n" +"Last-Translator: ralf401 \n" "Language-Team: German \n" +"documentations/admin-documentation-latest/de/>\n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" -"X-Generator: Weblate 4.16.4\n" +"X-Generator: Weblate 4.18.2\n" #: ../channels/chat.rst:2 msgid "Chat" @@ -271,7 +271,7 @@ msgstr "" #: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 #: ../channels/microsoft365/accounts.rst:2 msgid "Accounts" -msgstr "Accounts" +msgstr "Konten" #: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 #: ../channels/microsoft365/accounts.rst:32 @@ -678,7 +678,8 @@ msgstr "Port" #: ../channels/email/accounts/account-setup.rst:147 msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." msgstr "" -"Der Port Ihres E-Mail-Servers (usu. ``993`` für IMAP, oder ``995`` für POP3)." +"Der Port Ihres E-Mail-Servers (typischerweise ``993`` für IMAP, oder ``995`` " +"für POP3)." #: ../channels/email/accounts/account-setup.rst:173 #: ../channels/google/accounts/account-setup.rst:76 @@ -729,6 +730,9 @@ msgid "" "have to manually check your inbox during the verification step and move " "Zammad’s test message there when it arrives." msgstr "" +"Wenn in diesem Ordner keine eingehenden E-Mails landen, prüfen Sie bitte " +"manuell den Posteingang und verschieben die E-Mail in den Unterordner, " +"sobald sie ankommt." #: ../channels/email/accounts/account-setup.rst:197 #: ../channels/google/accounts/account-setup.rst:98 @@ -794,6 +798,9 @@ msgid "" "If you choose **yes** here, remember that it’s your responsibility to clean " "out your inbox from time to time to keep it below its storage limit." msgstr "" +"Wenn Sie hier **Ja** auswählen, bedenken Sie bitte, Ihren Posteingang " +"gelegentlich zu bereinigen. Andernfalls laufen Sie Gefahr, Speicherplatz-" +"Probleme zu bekommen." #: ../channels/email/accounts/account-setup.rst:226 msgid "Import as" @@ -801,7 +808,7 @@ msgstr "Importieren als" #: ../channels/email/accounts/account-setup.rst:0 msgid "“Import as” option in email account setup dialog" -msgstr "" +msgstr "\"Importieren als\" Option im E-Mail Einrichtungs-Dialog" #: ../channels/email/accounts/account-setup.rst:205 msgid "How should old emails be imported?" @@ -815,12 +822,19 @@ msgid "" "received and we’ll get back to you within 24 hours,” and tickets created for " "each message will be marked as “new”." msgstr "" +"Während des Import-Vorgangs behandelt Zammad **alle E-Mails** ( inklusive " +"solchen, die ggf. schon vor einiger Zeit eingegangen sind) als wie wenn " +"diese jetzt eingegangen wären: Absender bekommen eine automatische " +"Eingangsbestätigung , dass die E-Mail eingegangen ist. Für jede E-Mail wird " +"ein Ticket im Status \"neu\" angelegt." #: ../channels/email/accounts/account-setup.rst:214 msgid "" "Use this option to disable this behavior for messages more than two weeks " "old." msgstr "" +"Diese Option deaktiviert dieses Verhalten für E-Mails, die älter als zwei " +"Wochen sind." #: ../channels/email/accounts/account-setup.rst:217 msgid "This option may not be shown if:" @@ -832,11 +846,11 @@ msgstr "alle Nachrichten in Ihrem Posteingang sind weniger als zwei Wochen alt" #: ../channels/email/accounts/account-setup.rst:220 msgid "you selected **Keep messages on server: Yes**" -msgstr "" +msgstr "Sie haben **Nachrichten auf dem Server belassen: Ja** ausgewählt" #: ../channels/email/accounts/account-setup.rst:221 msgid "you selected **Type: POP3**" -msgstr "" +msgstr "Sie haben **Typ: POP3** ausgewählt" #: ../channels/email/accounts/account-setup.rst:223 msgid "" @@ -844,6 +858,9 @@ msgid "" "`triggers ` before adding an email account, then turn them " "back on once all your messages have been imported." msgstr "" +"Um keine unerwünschten Effekte auszulösen deaktivieren Sie das und andere :" +"doc:`triggers ` bevor Sie einen E-Mail-Konto hinzufügen, " +"dann schalten Sie diese wieder ein nachdem alle Mails importiert wurden." #: ../channels/email/accounts/account-setup.rst:229 msgid "Email Outbound" @@ -852,24 +869,28 @@ msgstr "Email ausgehend" #: ../channels/email/accounts/account-setup.rst:235 #: ../channels/email/accounts/email-notification.rst:21 msgid "Send mails via" -msgstr "" +msgstr "E-Mail verschicken über" #: ../channels/email/accounts/account-setup.rst:232 #: ../channels/email/accounts/email-notification.rst:21 msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." -msgstr "" +msgstr "Wählen Sie zwischen **SMTP** und **local MTA** (z.B. Sendmail)." #: ../channels/email/accounts/account-setup.rst:234 msgid "" "Local MTA (mail transfer agent) configuration is only available on self-" "hosted installations." msgstr "" +"Die Einstellungen für local MTA (mail transfer agent) ist nur in selbst " +"gehosteten Installationen verfügbar." #: ../channels/email/accounts/account-setup.rst:238 #: ../channels/email/accounts/email-notification.rst:24 msgid "" "Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." msgstr "" +"Der Hostname oder die IP-Adresse Ihren E-Mail-Servers (z.B. ``smtp.gmail." +"com``)." #: ../channels/email/accounts/account-setup.rst:241 #: ../channels/email/accounts/email-notification.rst:27 @@ -887,6 +908,8 @@ msgstr "" #: ../channels/email/accounts/email-notification.rst:36 msgid "Your email server’s port (usu. ``587`` or ``465``)." msgstr "" +"Der Port, auf dem Ihr E-Mail-Server erreichbar ist (typischerweise ``587`` " +"oder ``465``)." #: ../channels/email/accounts/account-setup.rst:253 #: ../channels/email/accounts/email-notification.rst:38 @@ -908,12 +931,18 @@ msgid "" "own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " "which discards the test mail right away." msgstr "" +"Im letzten Schritt prüft Zammad die Konfiguration, indem eine E-Mail von dem " +"angelegten Account an denselben Account geschickt wird und an ``verify-" +"external-smtp-sending@discard.zammad.org``, wo die Mail direkt verworfen " +"wird." #: ../channels/email/accounts/account-setup.rst:266 msgid "" "We've created a `landing page for discard.zammad.org`_ which describes the " "backgrounds as well." msgstr "" +"Wir haben eine `landing page for discard.zammad.org`_, welche den " +"Hintergrund erklärt." #: ../channels/email/accounts/account-setup.rst:272 msgid "" @@ -921,6 +950,9 @@ msgid "" "internal and external - once this is verified the setup process is complete! " "🎉" msgstr "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" #: ../channels/email/accounts/account-setup-group-hint.include.rst:1 msgid "🤓 **Don't forget to set the outgoing email address**" @@ -958,6 +990,8 @@ msgstr "Fehlerbehebung" msgid "" ":ref:`Is a custom incoming mail folder to blame? `" msgstr "" +":ref:`Ein Postfach-Unterordner für eingehende E-Mails? `" #: ../channels/email/accounts/email-notification.rst:2 msgid "Email Notification" @@ -992,16 +1026,20 @@ msgid "" "Use the **Email Notification** panel to configure how Zammad dispatches " "these notifications." msgstr "" +"Benutzen Sie die **E-Mail-Benachrichtigungs-Einstellungen**, um zu " +"konfigurieren, wie Zammad diese Benachrichtigungen versendet." #: ../channels/email/accounts/email-notification.rst:None msgid "Demonstration of email notification channel editing" -msgstr "" +msgstr "Demonstration Anpassung E-Mail-Benachrichtigung" #: ../channels/email/accounts/email-notification.rst:29 msgid "" "The “From:” address on system notifications can be configured under :doc:" "`Channels > Email > Settings > Notification Sender <../settings>`." msgstr "" +"Die \"Von:\" Adresse bei System-Benachrichtigungen kann unter :doc:`Channels " +"> Email > Settings > Notification Sender <../settings>` konfiguriert werden." #: ../channels/email/accounts/email-notification.rst:40 msgid "🤔 **This looks familiar... Where have I seen it before?**" @@ -1010,13 +1048,15 @@ msgstr "" #: ../channels/email/accounts/email-notification.rst:42 msgid "This configuration step was part of the Getting Started wizard:" -msgstr "" +msgstr "Diese Einstellung war Teil des Einrichtungsassistenten:" #: ../channels/email/accounts/email-notification.rst:0 msgid "" "The getting started wizard asking how one wants to send out\n" "notifications" msgstr "" +"Der Einrichtungsassistent fragt, wie Sie Benachrichtigungen verschicken " +"möchten" #: ../channels/email/accounts/managing-accounts.rst:2 msgid "Managing Accounts" @@ -1027,6 +1067,8 @@ msgid "" "Once an account has been added, use the Accounts panel to edit its " "configuration." msgstr "" +"Sobald ein Account hinzugefügt wurde können Sie den Konten-Dialog verwenden, " +"um die Einstellungen anzupassen." #: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 #: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 @@ -1038,22 +1080,26 @@ msgid "" "Click **Edit** on inbound/outbound account details to change your server " "configuration." msgstr "" +"Klicken Sie auf **Bearbeiten** bei \"Eingehend\"/\"Ausgehend\" in den " +"Kontoeinstellungen, um die Serverkonfiguration zu konfigurieren." #: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 msgid "" "See :ref:`New Account Settings ` for a detailed " "description of each option." msgstr "" +"Siehe :ref:`New Account Settings ` für eine " +"detaillierte Beschreibung der einzelnen Optionen." #: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 #: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 #: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 msgid "Location of account details settings for existing accounts" -msgstr "" +msgstr "Detaileinstellungen für existierende Konten" #: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 msgid "⌨️ In some browsers, you may have to manually re-enter your password." -msgstr "" +msgstr "⌨️ In manchen Browsern müssen Sie das Passwort mehrfach eingeben." #: ../channels/email/accounts/managing-accounts.rst:14 msgid "Click on the group name to reassign the account." @@ -1063,13 +1109,13 @@ msgstr "Klicken Sie auf den Gruppennamen, um das Konto neu zuzuordnen." #: ../channels/google/accounts/account-setup.rst:0 #: ../channels/microsoft365/accounts/account-setup.rst:0 msgid "Location of \"Destination Group\" setting for existing accounts" -msgstr "" +msgstr "Einstellungen der \"Empfängergruppe\" für existierende Konten" #: ../channels/email/accounts/managing-accounts.rst:21 #: ../channels/google/accounts/account-setup.rst:109 #: ../channels/microsoft365/accounts/account-setup.rst:171 msgid "Only **active** groups will be displayed." -msgstr "" +msgstr "Nur **aktive** Gruppen werden angezeigt." #: ../channels/email/accounts/managing-accounts.rst:23 #: ../channels/google/accounts/account-setup.rst:111 @@ -1077,67 +1123,82 @@ msgstr "" msgid "" "Changing this setting will not reassign existing tickets to the new group." msgstr "" +"Die Änderung dieser Einstellung wird bestehende Tickets keiner neuen Gruppe " +"zuordnen." #: ../channels/email/accounts/managing-accounts.rst:25 msgid "" "📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " "settings `." msgstr "" +"📮 **Sie können trotzdem keine E-Mails aus Tickets verschicken?** Prüfen Sie :" +"doc:`group settings `." #: ../channels/email/accounts/managing-accounts.rst:37 msgid "Email Address" -msgstr "" +msgstr "E-Mail-Adresse" #: ../channels/email/accounts/managing-accounts.rst:29 msgid "" "Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " "account." msgstr "" +"Benutzen Sie den **Bearbeiten** oder **Hinzufügen** Button, um dem Konto " +"eine weitere Mailadresse hinzuzufügen." #: ../channels/email/accounts/managing-accounts.rst:32 msgid "" "See :doc:`secondary-addresses` for a detailed description of each option." msgstr "" +"Siehe :doc:`secondary-addresses` für eine detaillierte Übersicht aller " +"Optionen." #: ../channels/email/accounts/managing-accounts.rst:0 msgid "Location of email address add/edit buttons" -msgstr "" +msgstr "E-Mail-Adresse hinzufügen / bearbeiten" #: ../channels/email/accounts/managing-accounts.rst:47 msgid "Enabled / Disabled" -msgstr "" +msgstr "Aktivieren / Deaktivieren" #: ../channels/email/accounts/managing-accounts.rst:40 msgid "" "Disabling an account temporarily prevents Zammad from importing its messages." msgstr "" +"Wenn Sie ein Konto vorübergehend deaktivieren wird Zammad keine Nachrichten " +"daraus importieren." #: ../channels/email/accounts/managing-accounts.rst:42 msgid "" "This may be necessary during scheduled maintenance or when migrating your " "installation to a new host." msgstr "" +"Das ist bei geplanten Wartungsarbeiten sinnvoll oder wenn Sie Ihre " +"Installation auf einen neuen Host migrieren." #: ../channels/email/accounts/managing-accounts.rst:47 msgid "📮 Disabling an account disables *outgoing* messages for it, as well." msgstr "" +"📮 Die Deaktivierung eines Kontos deaktiviert auch die darüber *ausgehenden* " +"Nachrichten." #: ../channels/email/accounts/managing-accounts.rst:51 #: ../channels/email/accounts/managing-accounts.rst:52 #: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 #: ../manage/knowledge-base.rst:195 msgid "Delete" -msgstr "" +msgstr "Löschen" #: ../channels/email/accounts/managing-accounts.rst:50 msgid "Deleting an account removes its configuration from Zammad entirely." msgstr "" +"Das Löschen eines Kontos löscht dessen gesamte Konfiguration in Zammad." #: ../channels/email/accounts/managing-accounts.delete-note.rst:1 #: ../channels/google/accounts/managing-accounts.delete-note.rst:1 #: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 msgid "🧹 **Additional Steps Required**" -msgstr "" +msgstr "🧹 **Zusätzliche Maßnahmen erforderlich**" #: ../channels/email/accounts/managing-accounts.delete-note.rst:3 msgid "" @@ -1145,17 +1206,22 @@ msgid "" "addresses>` **remain in the system**. Be sure to reassign or delete them " "manually." msgstr "" +"Wenn ein E-Mail-Account gelöscht wird, bleiben die E-Mail-Aliase :doc:`E-" +"Mail-Alias ` **im System erhalten**. Bitte stellen Sie " +"sich, diese einem Kanal zuzuweisen oder zu löschen." #: ../channels/email/accounts/managing-accounts.rst:0 #: ../channels/email/accounts/managing-accounts.delete-note.rst:0 msgid "List of orphaned email addresses" -msgstr "" +msgstr "Liste der nicht verwendeten E-Mail-Adressen" #: ../channels/email/accounts/managing-accounts.delete-note.rst:12 msgid "" "Click on the address to assign it to another account, or click ✖ to delete " "it." msgstr "" +"Klicken Sie auf die Adresse, um diese einem anderen Account zuzuweisen oder " +"klicken Sie ✖, um sie zu löschen." #: ../channels/email/accounts/managing-accounts.delete-note.rst:15 #: ../channels/google/accounts/managing-accounts.delete-note.rst:3 @@ -1165,28 +1231,38 @@ msgid "" "group’s assigned address, agents belonging to that group won’t be able to " "send emails until you assign it a new one." msgstr "" +"Gruppen benötigen eine zugewiesene E-Mail-Adresse, um Nachrichten zu " +"verschicken. Wenn Sie eine E-Mail-Adresse löschen, die einer Gruppe " +"zugewiesen ist, können deren Agenten keine Nachrichten mehr verschicken bis " +"Sie eine neue Zuweisung vornehmen." #: ../channels/email/accounts/secondary-addresses.rst:2 msgid "Secondary Addresses" -msgstr "" +msgstr "Zusätzliche Adresse" #: ../channels/email/accounts/secondary-addresses.rst:4 msgid "" "Secondary addresses (also known as *aliases*) allow you to send emails with " "a different “From:” address from the one on the account." msgstr "" +"Mit zusätzlichen E-Mail-Adressen (auch *Aliase* genannt) können Sie E-Mails " +"mit einer vom Konto abweichenden \"Von:\" Adresse verschicken." #: ../channels/email/accounts/secondary-addresses.rst:12 msgid "" "Video demonstration of adding a secondary address and configuring\n" "a group to use it." msgstr "" +"Video einer Einrichtung einer zusätzlichen E-Mail-Adresse und Konfiguration " +"der Gruppe." #: ../channels/email/accounts/secondary-addresses.rst:12 msgid "" "Once you add a secondary address, you can configure a group to start sending " "emails with it." msgstr "" +"Sobald Sie eine zusätzliche Adresse hinzugefügt haben, können Sie diese " +"einer Gruppe zuweisen, damit diese darüber E-Mails verschicken kann." #: ../channels/email/accounts/secondary-addresses.warning.rst:1 msgid "🙅 **Do not abuse this feature.**" @@ -1197,6 +1273,8 @@ msgid "" "If you use secondary addresses to impersonate other parties, your IP is " "liable to get added to a spam blacklist." msgstr "" +"Wenn Sie zusätzliche E-Mail-Adressen mit abweichender Domain verwenden, " +"laufen Sie Gefahr, auf einer Spam-Sperrliste zu landen." #: ../channels/email/accounts/secondary-addresses.rst:17 msgid "" @@ -1204,6 +1282,9 @@ msgid "" "many addresses in the same mailbox. If this is the case, be sure to add your " "alternate inbox addresses here." msgstr "" +"Ihr E-Mail-Anbieter unterstützt möglicherweise die Funktion, E-Mails für " +"andere E-Mail-Adressen in einem Postfach zu sammeln. Sofern das der Fall und " +"bei Ihnen eingerichtet ist, fügen Sie bitte die Adressen hier hinzu." #: ../channels/email/accounts/secondary-addresses.rst:32 msgid "Display Name" @@ -1243,11 +1324,11 @@ msgstr "" #: ../channels/email/advanced/fetchmail.rst:2 msgid "Watch your inbox with Fetchmail" -msgstr "" +msgstr "Rufen Sie Ihren Posteingang mit Fetchmail ab" #: ../channels/email/advanced/fetchmail.rst:4 msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." -msgstr "" +msgstr "Sie können E-Mails mit Fetchmail oder Procmail in Zammad hinzufügen." #: ../channels/email/advanced/fetchmail.rst:6 msgid "To get this to work you need to pipe your emails to rails." @@ -1260,6 +1341,10 @@ msgid "" "`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 `Administration via Console `_." #: ../channels/email/advanced/fetchmail.rst:15 msgid "**Command line**::" @@ -1271,12 +1356,12 @@ msgstr "Fetchmail" #: ../channels/email/advanced/fetchmail.rst:25 msgid "**Create .fetchmailrc**::" -msgstr "" +msgstr "**Create .fetchmailrc**::" #: ../channels/email/advanced/fetchmail.rst:33 #: ../channels/email/advanced/fetchmail.rst:53 msgid "**vi .fetchmailrc**::" -msgstr "" +msgstr "**vi .fetchmailrc**::" #: ../channels/email/advanced/fetchmail.rst:41 msgid "That's it. Emails now will be directly piped into Zammad." @@ -1284,29 +1369,31 @@ msgstr "" #: ../channels/email/advanced/fetchmail.rst:46 msgid "Using Procmail for advanced features like presorting" -msgstr "" +msgstr "Verwenden Sie Procmail für erweiterte Funktionen wie Vorsortierung" #: ../channels/email/advanced/fetchmail.rst:48 msgid "" "If you want to do some more with your emails, like presorting to a Zammad " "group or filtering spam, you can use Procmail." msgstr "" +"Wenn Sie mit Ihren E-Mails mehr machen wollen, z.B. Vorsortierung oder Spam-" +"Filterung, können Sie dafür Procmail verwenden." #: ../channels/email/advanced/fetchmail.rst:51 msgid "Fetchmail config looks slightly different." -msgstr "" +msgstr "Die Fetchmail-Konfiguration weicht ein wenig ab." #: ../channels/email/advanced/fetchmail.rst:61 msgid "**Create .procmailrc**::" -msgstr "" +msgstr "**Create .procmailrc**::" #: ../channels/email/advanced/fetchmail.rst:67 msgid "**vi .procmailrc**::" -msgstr "" +msgstr "**vi .procmailrc**::" #: ../channels/email/advanced/sendmail.rst:2 msgid "Dispatch messages with Sendmail" -msgstr "" +msgstr "Verschicken Sie E-Mails mit Sendmail" #: ../channels/email/advanced/sendmail.rst:6 msgid "" @@ -1321,6 +1408,10 @@ msgid "" "it’s simply not possible via the email channel setup wizard. Instead, you " "will have to create it via the CLI." msgstr "" +"Sofern Sie **nur** einen ausgehenden E-Mail-Kanal konfigurieren wollen (also " +"keine eingehendes IMAP/POP3-Konto), werden Sie feststellen, dass das über " +"den E-Mail-Einrichtungsassistent nicht möglich ist. Stattdessen müssen Sie " +"das über die Konsole konfigurieren." #: ../channels/email/advanced/sendmail.rst:14 msgid "" @@ -1328,44 +1419,57 @@ msgid "" "process for the average, non-technical user, so certain advanced options and " "use cases have been deliberately omitted.)" msgstr "" +"(Der Assistent ist so gestaltet, dass auch der durchschnittliche Benutzer " +"ohne tiefgreifende Technikkenntnisse einen E-Mail-Kanal einrichten kann. " +"Deshalb sind solche erweiterten Funktionen in der Oberfläche nicht möglich)" #: ../channels/email/advanced/sendmail.rst:18 msgid "" "To configure Zammad to use sendmail, run the following command (you can use " "rails r [...] if you installed Zammad from source)::" msgstr "" +"Um Zammad mit Sendmail zu nutzten, führen Sie folgenden Befehl aus (Sie " +"können rails r [...] nutzen, sofern Sie Zammad als Source-Installation " +"betreiben)::" #: ../channels/email/advanced/sendmail.rst:23 msgid "" "Now, you should see a new **Email Account** entry in the admin settings " "panel:" msgstr "" +"Nun sollten Sie einen neuen Eintrag unter **E-Mail-Konten** in den Admin-" +"Einstellungen sehen:" #: ../channels/email/advanced/sendmail.rst:30 msgid "" "The new, outbound-only email channel appears in the admin settings\n" "email panel." -msgstr "" +msgstr "Der neue ausgehende E-Mail-Kanal erscheint in den Admin-Einstellungen." #: ../channels/email/advanced/sendmail.rst:30 msgid "" "Use the **Add** button under the **Email Address** heading to add new email " "addresses to send from." msgstr "" +"Verwenden Sie den **Hinzufügen** Button unter **E-Mail-Adresse**, um eine " +"neue E-Mail-Adresse zum Versenden hinzuzufügen." #: ../channels/email/email-headers.rst:2 msgid "Email header manipulation" -msgstr "" +msgstr "E-Mail Header-Manipulation" #: ../channels/email/email-headers.rst:4 msgid "" "Email header manipulation allows you to re-route or adjust tickets apart " "from filters or triggers. Like an API call, but with emails." msgstr "" +"Die E-Mail Header-Manipulation erlaubt es, Tickets unabhängig von Filtern " +"und Triggern zu steuern." #: ../channels/email/email-headers.rst:7 msgid "Header checks are case insensitive." msgstr "" +"Header-Prüfungen unterscheiden nicht zwischen Groß- und Kleinschreibung." #: ../channels/email/email-headers.rst:9 msgid "**🛡 Trusted channels required 🛡**" @@ -1376,6 +1480,9 @@ msgid "" "Below options are a potential risk with external communication and thus " "require channels being set to trusted explicitly." msgstr "" +"Untenstehende Optionen bergen ein potenzielles Risiko hinsichtlich der " +"Kommunikation mit externen Parteien, weshalb der Kanal explizit als " +"vertrauenswürdig deklariert werden muss." #: ../channels/email/email-headers.rst:16 msgid "" @@ -1383,34 +1490,45 @@ msgid "" "However: You can adjust mostly any article or ticket attribute (yes, custom " "ones as well) if you know the attribute's exact name." msgstr "" +"Untenstehende Header sind Beispiele und - unserer Meinung nach - die " +"wichtigsten. Sie können allerdings die meisten Artikel- oder Ticket-" +"Attribute verändern (auch selbst erstellte), sofern Sie den Namen des " +"Attributs kennen." #: ../channels/email/email-headers.rst:20 msgid "" "The name column within :doc:`object's management ` provides " "easy access to objects attribute names. 🤓" msgstr "" +"In der Spalte \"Name\" in der :doc:`Objektverwaltung ` " +"können Sie die Namen der Attribute finden." #: ../channels/email/email-headers.rst:24 msgid "Trigger auto responses" -msgstr "" +msgstr "Automatische Antwort auslösen" #: ../channels/email/email-headers.rst:26 msgid "" "Normally Zammad runs internal checks to see if an email is an automatic " "response. In these cases Zammad will not send trigger based responses." msgstr "" +"Standardmäßig nimmt Zammad interne Prüfung vor, um zu prüfen, ob eine E-Mail " +"eine automatische Antwort ist. In einem solchen Fall wird Zammad keine " +"Trigger-basierte Antwort schicken." #: ../channels/email/email-headers.rst:29 msgid "" "There may be use cases where this behavior may be in your way, below options " "allow you to overcome this issue." msgstr "" +"Es könnte aber Anwendungsfälle geben, bei denen dieses Verhalten nicht " +"gewünscht ist. Mit der folgenden Option können Sie das Verhalten übersteuern." #: ../channels/email/email-headers.rst:34 msgid "" "In some cases combining below headers is crucial. This is intentional but " "may be confusing." -msgstr "" +msgstr "In einigen Fällen müssen untenstehende Header kombiniert werden." #: ../channels/email/email-headers.rst:44 msgid "``x-zammad-send-auto-response``" @@ -1421,12 +1539,16 @@ msgid "" "Set to ``false`` to disable trigger based responses. If set to ``true`` " "Zammad will send a response." msgstr "" +"Verwenden Sie ``false``, um Trigger-basierte Antworten zu deaktivieren. " +"Sofern Sie es auf ``true`` setzen, wird Zammad eine Antwort senden." #: ../channels/email/email-headers.rst:43 msgid "" "This option *does not* work if e.g. ``precedence: list`` is set unless you " "use below auto response header as well." msgstr "" +"Diese Funktion funktioniert *nicht*, wenn Sie zum Beispiel ``precedence: " +"list`` gesetzt haben ohne den folgenden Header zu benutzten." #: ../channels/email/email-headers.rst:56 msgid "``x-zammad-is-auto-response``" @@ -1438,16 +1560,23 @@ msgid "" "an auto generated response (``true``). This will cause email based triggers " "to be skipped." msgstr "" +"Wenn Sie diesen Header setzen weiß Zammad, dass die entsprechende E-Mail " +"eine automatisch generierte Antwort ist (``true``). Das verhindert die " +"Ausführung von E-Mail-basierten Triggern." #: ../channels/email/email-headers.rst:51 msgid "Set this header to ``false`` if you want to generate auto responses." msgstr "" +"Setzen Sie den Header auf ``false``, wenn eine automatische Antwort " +"generiert werden soll." #: ../channels/email/email-headers.rst:55 msgid "" "This header allows you to overwrite auto detects for e.g. ``precedence: " "list``." msgstr "" +"Dieser Header erlaubt es, die automatische Erkennung zum Beispiel für " +"``precedence: list`` zu übersteuern." #: ../channels/email/email-headers.rst:59 #: ../system/integrations/checkmk/api-reference.rst:52 @@ -1460,24 +1589,31 @@ msgid "" "ups. The manipulation can be used instead of triggers. Triggers are " "considered *after* header settings and thus can still overrule." msgstr "" +"In Zammad können Header-Veränderungen sowohl verwendet werden, um Tickets zu " +"generieren, als auch für Antworten auf Artikel. Die Header-Anpassung kann " +"anstatt den Triggern verwendet werden. Trigger werden *nach* dem Auslesen " +"der Header ausgeführt und können diese deshalb übersteuern." #: ../channels/email/email-headers.rst:65 msgid "**🔎 Zammad differentiates between ticket creation and follow up**" -msgstr "" +msgstr "**🔎 Zammad unterscheidet zwischen Ticket-Erstellung und Antworten**" #: ../channels/email/email-headers.rst:0 msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" -msgstr "" +msgstr "Verwenden Sie für die Erstellung: ``X-Zammad-Ticket-{Attribute Name}``" #: ../channels/email/email-headers.rst:0 msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" msgstr "" +"Verwenden Sie für Antworten: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" #: ../channels/email/email-headers.rst:70 msgid "" "This allows you to ensure the changes are only applied in the required " "situation." msgstr "" +"Das erlaubt es, die Änderungen nur in der erforderlichen Situation " +"auszuführen." #: ../channels/email/email-headers.rst:73 msgid "**🧐 About values**" @@ -1488,12 +1624,19 @@ msgid "" "While headers are not case sensitive, values like e.g. priority names are " "case censitive: ``1 low`` will work, but ``1 lOw`` will not!" msgstr "" +"Während bei den Headern nicht zwischen Groß- und Kleinschreibung " +"unterschieden wird, ist das bei den zugehörigen Werten, beispielsweise " +"Prioritätswerte, der Fall. ``1 niedrig`` ist korrekt, ``1 nIedrig`` wird " +"nicht korrekt erkannt." #: ../channels/email/email-headers.rst:77 msgid "" "When using attributes that require date / time values, ensure to use Time " "Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" msgstr "" +"Sofern Sie Attribute verwenden, die eine Datums-/Zeitangabe enthalten, " +"stellen Sie sicher, dass Sie Zeitzonen-Zeiten verwenden. Beispiel für 28. " +"September 2021, 8 Uhr:" #: ../channels/email/email-headers.rst:80 msgid "``2021-09-28T08:00:00+0200``" @@ -1513,7 +1656,7 @@ msgstr "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" #: ../channels/email/email-headers.rst:0 msgid "Allows you to adjust a ticket's priority." -msgstr "" +msgstr "Ermöglicht Ihnen die Anpassung der Ticket-Priorität." #: ../channels/email/email-headers.rst:0 msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" @@ -1525,7 +1668,7 @@ msgstr "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" #: ../channels/email/email-headers.rst:0 msgid "Allows you interfere with regular channel routing of the ticket." -msgstr "" +msgstr "Ermöglicht Ihnen, in die reguläre Gruppenzuweisung einzugreifen." #: ../channels/email/email-headers.rst:0 msgid "Example: ``X-Zammad-Ticket-Group: Sales``" @@ -1540,6 +1683,8 @@ msgid "" "Directly assign or change the ticket owner. Valid values are either " "``login`` or ``Email``" msgstr "" +"Weisen Sie ein Ticket direkt einem Besitzer zu oder ändern Sie diesen. " +"Gültige Werte sind entweder ``Login`` oder ``E-Mail``" #: ../channels/email/email-headers.rst:0 msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" @@ -1551,7 +1696,7 @@ msgstr "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" #: ../channels/email/email-headers.rst:0 msgid "Set a specific ticket state." -msgstr "" +msgstr "Setzen Sie einen bestimmten Ticket-Status." #: ../channels/email/email-headers.rst:0 msgid "Example: ``X-Zammad-Ticket-State: closed``" @@ -1575,6 +1720,8 @@ msgid "" "Manipulate the ticket customer - this can be a different user than the " "actual sender. Replying to the original sender is still possible." msgstr "" +"Verändern Sie den Kunden des Tickets. Das kann ein anderer Benutzer sein als " +"der Absender. Antworten an den Original-Absender sind weiterhin möglich." #: ../channels/email/email-headers.rst:0 msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" @@ -1602,6 +1749,8 @@ msgid "" "If needed Zammad allows you to manipulate attributes or states of fetched " "email articles." msgstr "" +"Zammad erlaubt es, die Attribute und den Status von Artikeln für bereits " +"abgerufene E-Mails zu verändern." #: ../channels/email/email-headers.rst:142 msgid "``X-Zammad-Article-Sender``" @@ -1609,7 +1758,7 @@ msgstr "``X-Zammad-Article-Sender``" #: ../channels/email/email-headers.rst:0 msgid "Manipulate the sender type (Agent, Customer, or System)" -msgstr "" +msgstr "Verändern Sie den Absender-Typ (Agent, Kunde oder System)" #: ../channels/email/email-headers.rst:0 msgid "Example: ``X-Zammad-Article-Sender: System``" @@ -1620,10 +1769,12 @@ msgid "" "System Emails are indicated in a similar way as trigger-response like " "entries Users can't see them natively." msgstr "" +"System E-Mails werden ähnlich wie Trigger-Aktionen dargestellt. Das heißt " +"Benutzer können die Artikel nicht komplett sehen." #: ../channels/email/email-headers.rst:0 msgid "Received mail as article sender system" -msgstr "" +msgstr "Eingehende E-Mail als Artikel vom Absender-Typ System" #: ../channels/email/email-headers.rst:152 msgid "``X-Zammad-Article-Type``" @@ -1634,6 +1785,8 @@ msgid "" "Change the article type of your incoming mail. This requires you to know " "which article types are available in your system." msgstr "" +"Ändert den Artikel-Typ von eingehenden E-Mails. Das setzt voraus, dass Sie " +"wissen welche Artikel-Typen in Ihrem System verfügbar sind." #: ../channels/email/email-headers.rst:0 msgid "Example: ``X-Zammad-Article-Type: phone``" @@ -1644,6 +1797,9 @@ msgid "" "This header can cause *serious issues* in your instance and may lead to " "unexpected behavior. Only use with absolute care!" msgstr "" +"Dieser Header kann **unerwünschte Auswirkungen** in Ihrer Zammad-Instanz " +"haben und zu unerwartetem Verhalten führen. Nutzen Sie diesen mit absoluter " +"Vorsicht!" #: ../channels/email/email-headers.rst:156 msgid "``X-Zammad-Article-Internal``" @@ -1651,7 +1807,7 @@ msgstr "``X-Zammad-Article-Internal``" #: ../channels/email/email-headers.rst:0 msgid "Manipulate the default article visibility." -msgstr "" +msgstr "Verändert die Sichtbarkeit (intern/öffentlich) des Artikels." #: ../channels/email/email-headers.rst:0 msgid "Example: ``X-Zammad-Article-Internal: true``" @@ -1664,7 +1820,7 @@ msgstr "``X-Zammad-Ignore``" #: ../channels/email/email-headers.rst:0 msgid "Tell Zammad to silently drop the Email." -msgstr "" +msgstr "Weist Zammad an, die E-Mail zu verwerfen." #: ../channels/email/email-headers.rst:0 msgid "Example: ``X-Zammad-Ignore: true``" @@ -1677,7 +1833,7 @@ msgstr "Filter" #: ../channels/email/filters.rst:None ../channels/email/settings.rst:None #: ../channels/email/signatures.rst:None msgid "Account settings page" -msgstr "" +msgstr "Kontoeinstellungen" #: ../channels/email/filters.rst:13 msgid "" @@ -1686,6 +1842,11 @@ msgid "" "Zammad's email parser encounters a matching email. The actions will be " "applied to the ticket that is created or updated by this email." msgstr "" +"Mit Postmaster-Filtern können Sie E-Mail-Header prüfen (z.B. ``Von``, " +"``An``, ``Betreff``, ``X-Spam-Flag`` etc.) und eine Reihe von Aktionen " +"ausführen, sobald die E-Mail-Verarbeitung in Zammad einen Treffer erkennt. " +"Die Aktionen werden auf das Ticket bezogen, das durch diese E-Mail erstellt " +"oder aktualisiert wird." #: ../channels/email/filters.rst:18 msgid "" @@ -1693,20 +1854,25 @@ msgid "" "might be useful for you what they actually do. Learn more on :doc:`filters/" "system-filters`" msgstr "" +"Zammad wird auch mit System-Filtern ausgeliefert. Obwohl Sie diese nicht " +"ändern können, kann das Wissen über deren Funktion dennoch nützlich sein. " +"Weitere Infos finden Sie unter :doc:`filters/system-filters`" #: ../channels/email/filters.rst:22 msgid "Here are some examples of what is possible with filters:" -msgstr "" +msgstr "Hier einige Beispiele, was mit Filtern möglich ist:" #: ../channels/email/filters.rst:35 msgid "Automatically dispatch tickets into certain groups:" -msgstr "" +msgstr "Automatisches Verteilen von Tickets in bestimmte Gruppen:" #: ../channels/email/filters.rst:25 msgid "" "For example, tickets from ``amazon.com`` could automatically be dispatched " "to the Purchasing group." msgstr "" +"Zum Beispiel könnten Tickets von ``amazon.com`` automatisch in die Gruppe " +"\"Einkauf\" verschoben werden." #: ../channels/email/filters.rst:0 msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" @@ -1722,10 +1888,13 @@ msgid "" "results in a new ticket. Zammad will not change the group of existing " "tickets." msgstr "" +"Bitte beachten Sie, dass Gruppen-Aktionen nur ausgeführt werden, wenn die E-" +"Mail ein neues Ticket generiert. Zammad wird keine Änderung der Guppe für " +"bestehende Tickets vornehmen." #: ../channels/email/filters.rst:45 msgid "Automatically increase the priority of tickets from a VIP customer:" -msgstr "" +msgstr "Erhöht automatisch die Priorität von Tickets eines VIP-Kunden:" #: ../channels/email/filters.rst:0 msgid "From: contains: ``ourvipcustomer@example.com``" @@ -1741,12 +1910,17 @@ msgid "" "results in a new ticket. Zammad will not change the priority of existing " "tickets." msgstr "" +"Beachten Sie, dass die Anpassung der Priorität eines Tickets nur bei neu " +"erstellten Tickets berücksichtigt wird. Zammad ändert die Priorität bei " +"bestehenden Ticket nicht." #: ../channels/email/filters.rst:57 msgid "" "Automatically tag and close spam tickets that have been marked as spam by " "anexternal spam filter (e.g. SpamAssassin):" msgstr "" +"Automatisches Kennzeichnen als Spam und Schließen von Tickets, die von einem " +"externen Spamfilter (z.B. SpamAssassin) entsprechend gekennzeichnet wurden:" #: ../channels/email/filters.rst:0 msgid "X-Spam-Flag: contains: ``YES``" @@ -1754,11 +1928,11 @@ msgstr "X-Spam-Flag: enthält: ``JA``" #: ../channels/email/filters.rst:0 msgid "Tag: add: ``spam``" -msgstr "" +msgstr "Tag: *hinzufügen:* ``spam``" #: ../channels/email/filters.rst:0 msgid "State: closed" -msgstr "" +msgstr "Status: geschlossen" #: ../channels/email/filters.rst:54 msgid "" @@ -1767,10 +1941,14 @@ msgid "" "tickets. It will add the tag though if it missing, even if the mail is an " "update to an existing ticket." msgstr "" +"Beachten Sie, dass die Anpassung des Status eines Tickets nur bei neu " +"erstellten Tickets berücksichtigt wird. Zammad ändert den Status bei " +"bestehenden Ticket nicht. Der Tag hingegen wird auch bei einer " +"Aktualisierung eines Tickets hinzugefügt." #: ../channels/email/filters.rst:59 msgid "The following actions are only effective when creating tickets:" -msgstr "" +msgstr "Die folgenden Aktionen funktionieren nur bei der Ticketerstellung:" #: ../channels/email/filters.rst:61 #: ../system/integrations/checkmk/admin-panel-reference.rst:15 @@ -1798,6 +1976,11 @@ msgid "" "\" and \"contains not\"; for advanced matching, you can use regular " "expressions by prefixing the string with ``regex:``." msgstr "" +"Verschiedene Attribute können in den Filtern kombiniert werden. Die " +"unterstützen Kombinationen funktionieren mit den Parametern \"enthält\" und " +"\"enthält nicht\". Für eine tiefgreifendere Logik können sogenannten " +"reguläre Ausdrücke (regular expression) verwendet werden, die mit einem " +"vorangestellten ``regex:`` beginnen." #: ../channels/email/filters.rst:71 msgid "" @@ -1807,6 +1990,12 @@ msgid "" "especially important when using anchored regular expressions; ``regex:" "^display\\.name@example.com$`` would not match this mail!" msgstr "" +"Beachten Sie, dass Zammad den kompletten Header prüft. Beispielsweise prüft " +"Zammad bei einer E-Mail mit dem Header ``Von: Display Name `` den kompletten Inhalt, also ``Display Name ``. Das ist insbesondere dann wichtig, wenn Sie reguläre " +"Ausdrücke verwenden. Zum Beispiel würde die Regel ``regex:^display\\." +"name@example.com$`` keinen Treffer ergeben!" #: ../channels/email/filters.rst:77 msgid "" @@ -1814,12 +2003,12 @@ msgid "" "If a filter is no longer needed, it can either be temporarily set inactive " "or deleted directly." msgstr "" +"Beachten Sie, dass die Filter aufeinander aufbauen. Sofern ein Filter nicht " +"mehr benötigt wird, können Sie diesen entweder deaktivieren oder löschen." #: ../channels/email/filters/system-filters.rst:2 -#, fuzzy -#| msgid "Filters" msgid "System Filters" -msgstr "Filter" +msgstr "Systemfilter" #: ../channels/email/filters/system-filters.rst:4 msgid "" @@ -1827,34 +2016,42 @@ msgid "" "within the Zammad's UI. Those filters might come in handy when trying to " "understand Zammad's behavior." msgstr "" +"Auf dieser Seite finden Sie vordefinierte Filter, die nicht in Zammad " +"enthalten sind. Diese können nützlich sein, um die Funktionsweise zu " +"verstehen." #: ../channels/email/filters/system-filters.rst:10 msgid "" "Please note that this is not a full filters list, if you're missing filters, " "feel free to ask over at the `Community`_." msgstr "" +"Es handelt sich hierbei nicht um eine vollständige Filterliste. Sofern Sie " +"hier Filter vermissen, können Sie gerne in der `Community`_ eine Anfrage " +"stellen." #: ../channels/email/filters/system-filters.rst:16 msgid "JIRA" -msgstr "" +msgstr "JIRA" #: ../channels/email/filters/system-filters.rst:18 msgid "" "Zammad will detect Service Now emails and assign them to existing tickets, " "if the following requirements are met:" msgstr "" +"Zammad erkennt Service Now E-Mails und ordnet diese existierenden Tickets " +"zu, sofern folgende Voraussetzungen erfüllt sind:" #: ../channels/email/filters/system-filters.rst:21 msgid "Headers contain the ``X-ServiceNow-Generated`` header." -msgstr "" +msgstr "Header enthält ``X-ServiceNow-Generated``." #: ../channels/email/filters/system-filters.rst:22 msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." -msgstr "" +msgstr "Titel enthält regex ``\\s(INC\\d+)\\s`` z.B. ``INC678439``." #: ../channels/email/filters/system-filters.rst:24 msgid "See `JIRA Mail Example`_ for comparison of your emails." -msgstr "" +msgstr "Siehe `JIRA Mail Example`_ für einen Vergleich mit Ihren E-Mails." #: ../channels/email/filters/system-filters.rst:27 #, fuzzy @@ -1867,24 +2064,29 @@ msgid "" "Zammad will detect JIRA emails and assign them to existing tickets, if the " "following requirements are met:" msgstr "" +"Zammad erkennt JIRA E-Mails und ordnet diese existierenden Ticket zu, sofern " +"folgende Bedingungen erfüllt sind:" #: ../channels/email/filters/system-filters.rst:32 msgid "Headers contain the ``X-JIRA-FingerPrint`` header." -msgstr "" +msgstr "Headers enthält ``X-JIRA-FingerPrint``." #: ../channels/email/filters/system-filters.rst:33 msgid "" "Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " "``[JIRA] (SYS-422)``." msgstr "" +"Titel entspricht ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` z.B. ``[JIRA] " +"(SYS-422)``." #: ../channels/email/filters/system-filters.rst:36 msgid "See `Service-Now Mail Example`_ for comparison of your emails." msgstr "" +"Siehe `Service-Now Mail Example`_ für einen Vergleich mit Ihren E-Mails." #: ../channels/email/index.rst:13 msgid "Control how Zammad **sends and receives email**." -msgstr "" +msgstr "Legen Sie fest, wie Zammad **Mails sendet und empfängt**." #: ../channels/email/index.rst:18 msgid "**Using Gmail / G Suite?**" @@ -1893,128 +2095,146 @@ msgstr "**Sie benutzen Gmail / G-Suite?**" #: ../channels/email/index.rst:18 msgid "Set up a :doc:`Google channel ` instead." msgstr "" +"Nutzen Sie stattdessen den :doc:`Google Kanal `." #: ../channels/email/index.rst:21 msgid "**Using Microsoft 365?**" -msgstr "" +msgstr "**Nutzen Sie Microsoft 365?**" #: ../channels/email/index.rst:21 msgid "" "Set up a :doc:`Microsoft 365 channel ` instead." msgstr "" +"Nutzen Sie stattdessen den :doc:`Microsoft 365 Kanal `." #: ../channels/email/index.rst:None ../channels/google/index.rst:None #: ../channels/microsoft365/index.rst:None msgid "Email settings panel" -msgstr "" +msgstr "E-Mail Einstellungen" #: ../channels/email/index.rst:37 msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" msgstr "" +"🚛 Richten Sie einen existierenden E-Mail-Kanal als \"XOAUTH\" Kanal ein" #: ../channels/email/index.rst:29 msgid "At this moment Zammad supports XOAUTH for the following providers:" -msgstr "" +msgstr "Aktuell unterstützt Zammad XOAUTH für folgende Anbieter:" #: ../channels/email/index.rst:31 msgid ":doc:`Google `" -msgstr "" +msgstr ":doc:`Google `" #: ../channels/email/index.rst:32 msgid "" ":doc:`Microsoft 365 (formerly Office 365) `" msgstr "" +":doc:`Microsoft 365 (früher Office 365) `" #: ../channels/email/index.rst:34 msgid "" "Use above links to use the migration option instead of removing and re-" "adding the channels. This will save precious time for something else!" msgstr "" +"Verwenden Sie die Links, um die Migration eines Kanals zu verwenden, statt " +"diesen zu löschen und neu hinzuzufügen. Das spart Ihnen Zeit für wichtigere " +"Dinge!" #: ../channels/email/index.rst:44 ../channels/email/index.rst:8 msgid ":doc:`👥 Accounts `" -msgstr "" +msgstr ":doc:`👥 Konten `" #: ../channels/email/index.rst:40 ../channels/email/index.rst:4 msgid "" "**Connect Zammad to your email provider** so that it can watch your inbox, " "send auto-replies, and more." msgstr "" +"**Verbinden Sie Zammad mit Ihrem E-Mail-Konto**, damit es Ihren Posteingang " +"überwachen kann, Eingangsbestätigungen verschicken kann und mehr." #: ../channels/email/index.rst:43 ../channels/email/index.rst:7 msgid "" "(Self-hosted users may have already completed this step during new system " "setup.)" msgstr "" +"(Nutzer einer selbst gehosteten Instanz haben diese Schritte bereits während " +"der Einrichtung gemacht.)" #: ../channels/email/index.rst:48 ../channels/email/index.rst:12 msgid ":doc:`🗂️ Filters `" -msgstr "" +msgstr ":doc:`🗂️ Filter `" #: ../channels/email/index.rst:47 ../channels/email/index.rst:11 msgid "" "**Make sure new tickets show up in the right place** with automated, if-this-" "then-that rules for all incoming email." msgstr "" +"Richten Sie Automatisierungen mit Wenn-Dann-Regeln ein und stellen damit " +"sicher, dass **neue Tickets an die richtige Stelle gelangen**." #: ../channels/email/index.rst:51 ../channels/email/index.rst:15 msgid ":doc:`📜 Signatures `" -msgstr "" +msgstr ":doc:`📜 Signaturen `" #: ../channels/email/index.rst:51 ../channels/email/index.rst:15 msgid "Customize signatures for all outgoing email." -msgstr "" +msgstr "Anpassung von Signaturen für alle ausgehenden E-Mails." #: ../channels/email/index.rst:63 ../channels/email/index.rst:27 msgid ":doc:`⚙️ Settings `" -msgstr "" +msgstr ":doc:`⚙️ Einstellungen `" #: ../channels/email/index.rst:54 ../channels/email/index.rst:18 msgid "Manage options like:" -msgstr "" +msgstr "Passen Sie folgende Einstellungen an:" #: ../channels/email/index.rst:56 ../channels/email/index.rst:20 msgid "set the “From:” address on system notifications" -msgstr "" +msgstr "definieren Sie die \"Von:\" Adresse bei System-Benachrichtigungen" #: ../channels/email/index.rst:57 ../channels/email/index.rst:21 msgid "raise the limit on attachment sizes" -msgstr "" +msgstr "erhöhen Sie das Größenlimit für Anhänge" #: ../channels/email/index.rst:58 ../channels/email/index.rst:22 msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" -msgstr "" +msgstr "passen Sie den Präfix im Betreff an (*z.B.* \"\"AW:\" anstatt \"RE:\")" #: ../channels/email/index.rst:60 ../channels/email/index.rst:24 msgid "" "Want to **manually edit email subjects** or **always copy parent messages " "into your replies**?" msgstr "" +"**Wollen Sie den E-Mail-Betreff manuell anpassen** oder **immer die " +"Ursprungsnachricht in den Antworten zitieren**?" #: ../channels/email/index.rst:63 ../channels/email/index.rst:27 msgid "Check the ✍️ :doc:`/misc/composer`." -msgstr "" +msgstr "Schauen Sie sich ✍️ :doc:`/misc/composer` an." #: ../channels/email/index.rst:68 ../channels/email/index.rst:33 msgid ":doc:`📇 Header manipulation `" -msgstr "" +msgstr ":doc:`📇 Header Anpassung `" #: ../channels/email/index.rst:66 ../channels/email/index.rst:30 msgid "Manipulate auto response behavior or incoming routing." msgstr "" +"Passen Sie automatische Antworten an oder das Routing für eingehende Mails." #: ../channels/email/index.rst:68 ../channels/email/index.rst:32 msgid "🤓 This is a very advanced topic." -msgstr "" +msgstr "🤓 Das ist ein sehr spezielles Thema." #: ../channels/email/index.rst:71 msgid "Extra Options for Self-Hosted Users" -msgstr "" +msgstr "Extra Optionen für Nutzer einer selbst gehosteten Instanz" #: ../channels/email/index.rst:73 msgid "If you’re too cool for POP3/IMAP/SMTP..." -msgstr "" +msgstr "Wenn Sie zu cool für POP3/IMAP/SMTP sind..." #: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 #: ../system/integrations/checkmk/admin-panel-reference.rst:5 @@ -2026,22 +2246,29 @@ msgid "" "Below you can find the currently available email-related settings. Most of " "these settings have default values which can be found in this list as well." msgstr "" +"Unten finden Sie die aktuell verfügbaren E-Mail bezogenen Einstellungen. Die " +"meisten dieser Einstellungen haben Standardeinstellung, die Sie ebenfalls in " +"der Liste finden." #: ../channels/email/settings.rst:13 msgid "" "Some email-related settings are ticket-based settings, which is why they can " "be found in the :doc:`/misc/composer`." msgstr "" +"Einige der E-Mail-Einstellungen sind Ticket-basierte Einstellungen, weshalb " +"Sie diese unter :doc:`/misc/composer` finden können." #: ../channels/email/settings.rst:17 msgid "List of Settings" -msgstr "" +msgstr "Liste der Einstellungen" #: ../channels/email/settings.rst:28 msgid "" "Notification Sender: Default value ``Notification Master ``" msgstr "" +"Benachrichtigungs-Absender: Standardwert ``Notification Master " +"``" #: ../channels/email/settings.rst:20 msgid "" @@ -2050,16 +2277,23 @@ msgid "" "Your customers normally will not see this address. This email address does " "not need to receive and can't be assigned to a group." msgstr "" +"Das ist die standardmäßige Absenderadresse in Zammad, die für alle " +"Benachrichtigungen verwendet wird (nicht für Antworten von Agenten oder " +"Trigger-basierte Antworten). Ihre Kunden werden diese E-Mail-Adresse " +"normalerweise nicht zu sehen bekommen. Sie muss außerdem nicht zwingend " +"Mails empfangen können und kann keiner Gruppe zugewiesen werden." #: ../channels/email/settings.rst:27 msgid "" "This address is relevant for agent notifications and password reset mails " "(also affects customers)." msgstr "" +"Diese E-Mail-Adresse wird für die Benachrichtigung von Agenten und zum " +"Zurücksetzen des Passworts verwendet (betrifft hier ggf. auch Kunden)." #: ../channels/email/settings.rst:39 msgid "Additional follow-up detection" -msgstr "" +msgstr "Erweiterte Nachfrage-Erkennung" #: ../channels/email/settings.rst:31 msgid "" @@ -2067,16 +2301,22 @@ msgid "" "be due to missing references in the subject (the ticket hook and number). " "These options can help to recognize follow-ups to existing tickets." msgstr "" +"In manchen Szenarien ist die normale Nachfrage-Erkennung nicht ausreichend. " +"Das kann beispielsweise sein, wenn im Betreff die Ticket-Referenz (Ticket " +"hook und Nummer) fehlt. Das Einschalten dieser Option hilft, auch in solchen " +"Fällen eine Zuordnung von E-Mails zu bestehenden Tickets zu bekommen." #: ../channels/email/settings.rst:38 msgid "" "Please note that searching in attachment and body might lead to false follow-" "up detection." msgstr "" +"Bitte beachten Sie, dass die Suche im E-Mail-Body und im Anhang zu einer " +"falschen Nachfrage-Erkennung führen kann." #: ../channels/email/settings.rst:48 msgid "Maximum Email Size: Default value ``10 MB``" -msgstr "" +msgstr "Maximale E-Mail-Größe: Standardwert ``10 MB``" #: ../channels/email/settings.rst:42 msgid "" @@ -2084,24 +2324,31 @@ msgid "" "Zammad will fetch. Zammad will not fetch Mails that are bigger than this " "option." msgstr "" +"Diese Einstellung legt die maximale Größe für eine E-Mail fest, die Zammad " +"abrufen wird. Zammad wird keine Mails abrufen, die größer als der angegebene " +"Wert sind." #: ../channels/email/settings.rst:48 msgid "This technically also affects attachments for articles." -msgstr "" +msgstr "Das betrifft auch Anhänge für Artikel." #: ../channels/email/settings.rst:74 msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" msgstr "" +"Versendet eine Postmaster E-Mail, sofern die E-Mail zu groß ist. " +"Standardwert ``ja``" #: ../channels/email/settings.rst:53 msgid "" "Upgraded installations will, by default, have the value set to ``no " "(disabled``)." msgstr "" +"In Installationen, die upgedatet wurden, ist der Standardwert ``nein " +"(deaktiviert)``." #: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 msgid "Option set to ``yes``" -msgstr "" +msgstr "Option ist auf ``ja`` gesetzt" #: ../channels/email/settings.rst:57 msgid "" @@ -2109,6 +2356,9 @@ msgid "" "the above mail size limit with a postmaster style mail. This will help your " "user to understand that his mail did not arrive and won't be reviewed by you." msgstr "" +"Mit dieser Einstellung wird Zammad automatisch Antworten im Postmaster-Style " +"verschicken, sofern E-Mails die Größenbegrenzung überschreiten. Das gibt den " +"Kunden die Möglichkeit, die E-Mail erneut zu senden (mit reduzierter Größe)." #: ../channels/email/settings.rst:64 msgid "" @@ -2116,10 +2366,13 @@ msgid "" "mailbox. Instead of importing it to the database, it will save the affected " "mail to ``/opt/zammad/tmp/oversized_mail/``." msgstr "" +"Zammad wird die Mail trotzdem herunterladen und aus dem Posteingang " +"entfernen (sofern aktiviert). Allerdings wird die Mail nicht in Zammad " +"importiert, sondern unter ``/opt/zammad/tmp/oversized_mail/`` gespeichert." #: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 msgid "Option set to ``no``" -msgstr "" +msgstr "Option ist auf ``nein`` gestellt" #: ../channels/email/settings.rst:69 msgid "" @@ -2128,6 +2381,10 @@ msgid "" "Zammad will use the monitoring endpoint to alert its administrators that it " "can't fetch a too large mail." msgstr "" +"Wenn diese Option auf nein eingestellt ist, wird Zammad keine " +"Benachrichtigungen verschicken, dass die Mails zu groß sind. D.h. Ihre " +"Kunden werden **nicht mitbekommen**, dass Mails zu groß sind. Zammad wird " +"die Administratoren jedoch über die Monitoring-Funktion benachrichtigen." #: ../channels/email/settings.rst:74 msgid "Learn more about :doc:`/system/monitoring`." @@ -2136,6 +2393,7 @@ msgstr "Lernen Sie mehr über :doc:`/system/monitoring`." #: ../channels/email/settings.rst:88 msgid "Sender based on Reply-To header: Default value ``not set (-)``" msgstr "" +"Absender basierend auf Reply-To-Header: Standardwert ``nicht gesetzt (-)``" #: ../channels/email/settings.rst:77 msgid "" @@ -2143,22 +2401,31 @@ msgid "" "that contain a ``Reply-To`` header. This comes in useful if you're working " "with contact forms that need to use reply to headers." msgstr "" +"Mit dieser Einstellung kann festgelegt werden, wie Zammad Ihre Kunden in " +"einer E-Mail erkennt, die einen ``Reply-To`` Header angegeben haben. Das " +"kann z.B. nützlich sein, wenn Sie mit einem Formular arbeiten, das ``Reply-" +"To`` Header übergibt." #: ../channels/email/settings.rst:83 msgid "Option set to ``Take reply-to header as sender/from of email.``" msgstr "" +"Option gesetzt auf ``Nutze \"Reply-To\"-Feld als Absender einer E-Mail.``" #: ../channels/email/settings.rst:82 msgid "" "This setting will overwrite the initial ``FROM`` to the value used in " "``Reply-To`` completely." msgstr "" +"Diese Einstellung überschreibt den ``Von``-Wert mit dem , der in ``Reply-" +"To`` steht." #: ../channels/email/settings.rst:88 msgid "" "Option set to ``-`` or ``Take Reply-To header as sender/from of email and " "use the real name of origin from.``" msgstr "" +"Option gesetzt auf ``-`` oder ``Nutze \"Reply-To\"-Feld als Absender einer E-" +"Mail, aber den angezeigten Namen des \"From\"-Feldes.``" #: ../channels/email/settings.rst:86 msgid "" @@ -2166,26 +2433,34 @@ msgid "" "address from the ``Reply-To`` header and uses the given name of the ``FROM`` " "header, if given." msgstr "" +"Diese Einstellung überschreibt das ``Von``-Feld teilweise. Es wird die E-" +"Mail-Adresse des ``Reply-To``-Feldes in Kombination mit den Namen aus dem " +"``Von``-Feld verwendet." #: ../channels/email/settings.rst:104 msgid "" "Customer selection based on sender and receiver list: Default value ``yes``" msgstr "" +"Kundenauswahl basierend auf Sender- und Empfängerliste. Standardwert: ``ja``" #: ../channels/email/settings.rst:91 msgid "" "This option decides how Zammad should react if an agent sends a email to it." msgstr "" +"Diese Einstellung legt fest, wie mit E-Mails umgegangen wird, die von " +"Agenten an Zammad geschickt werden." #: ../channels/email/settings.rst:94 msgid "" "The first user / email address from the recipient list will be used as the " "ticket customer." msgstr "" +"Wenn der Sender ein Agent ist, wird der erste Benutzer in der Empfängerliste " +"als Kunde eingestellt." #: ../channels/email/settings.rst:98 msgid "The agent will be set as ticket customer." -msgstr "" +msgstr "Der Agent wird als Kunde gesetzt." #: ../channels/email/settings.rst:102 msgid "" @@ -2193,10 +2468,14 @@ msgid "" "works, agents can't see their own tickets (as a customer) if they don't have " "access to the group." msgstr "" +"Agenten können über die Oberfläche keine Tickets als Kunde anlegen. Bei per " +"E-Mail eingehenden Anfragen ist das hingegen möglich. Die Agenten können " +"dann Ihr Ticket (als Kunde) sehen, auch wenn Sie keine Berechtigung für die " +"Gruppe haben." #: ../channels/email/settings.rst:114 msgid "Block Notifications" -msgstr "" +msgstr "Benachrichtigungen stoppen" #: ../channels/email/settings.rst:107 msgid "" @@ -2204,24 +2483,33 @@ msgid "" "notifications to specific systems. By default this especially affects " "typical system addresses which can't receive emails anyway." msgstr "" +"Mit dieser Regex kann definiert werden, an welche E-Mail-Adressen keine " +"Benachrichtigungen geschickt werden. Standardmäßig sind hier bereits " +"typische Adressen angelegt, die sowieso keine E-Mails empfangen können." #: ../channels/email/settings.rst:111 msgid "" "The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." "+?|no-reply|no-reply.+?)@.+?``" msgstr "" +"Standardwert ist: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply.+?|" +"no-reply|no-reply.+?)@.+?``" #: ../channels/email/settings.rst:146 msgid "" "Sender Format: Default value ``Agent Name + FromSeparator + System Address " "Display Name``" msgstr "" +"Absender-Format. Standardwert: ``Name des Agenten + Von-Trenner + " +"Anzeigename der Systemadresse``" #: ../channels/email/settings.rst:117 msgid "" "This configures the display name used in the ``FROM`` header of mails Zammad " "sends." msgstr "" +"Diese Einstellung definiert den Anzeigename, der im ``Von``-Header von " +"Zammad in ausgehenden E-Mails verwendet wird." #: ../channels/email/settings.rst:122 msgid "" @@ -2229,91 +2517,111 @@ msgid "" "mails. Emails that are not sent by agents (e.g. trigger-based notifications) " "will always fallback to ``System Address Display Name`` if needed." msgstr "" +"Das betrifft nicht Mailbenachrichtigungen an Agenten und E-Mails zum " +"Zurücksetzen des Passworts. E-Mails, welche nicht von Agenten verschickt " +"werden (z.B. Trigger-basierte Benachrichtigungen), verwenden immer vom " +"``Anzeigename System-Adresse ``." #: ../channels/email/settings.rst:131 msgid "" "Option set to ``Agent Name + FromSeparator + System Address Display Name``" msgstr "" +"Einstellung auf ``Name des Agenten + Von-Trenner + Anzeigename der " +"Systemadresse`` gesetzt" #: ../channels/email/settings.rst:128 msgid "" "This will cause Zammad to set the ``FROM`` header to agent name and the " "channel's display name, divided by a separator (configured below)." msgstr "" +"Zammad setzt damit den Namen des Agenten und den System-Namen in den ``Von`` " +"Header, getrennt durch ein Trennzeichen (siehe folgende Konfiguration)." #: ../channels/email/settings.rst:131 msgid "Example: ``Christopher Miller via Chrispresso Inc.``." -msgstr "" +msgstr "Beispiel: ``Christopher Miller via Chrispresso Inc.``." #: ../channels/email/settings.rst:137 msgid "Option set to ``System Address Display Name``" -msgstr "" +msgstr "Einstellung auf ``Anzeigename der Systemadresse``" #: ../channels/email/settings.rst:134 msgid "" "This will cause Zammad to always use the display name of the used channel in " "the ``FROM`` header." msgstr "" +"Dadurch wird Zammad immer den Namen des E-Mail-Kanals der jeweiligen Gruppe " +"in den ``Von`` Header eintragen." #: ../channels/email/settings.rst:137 msgid "Example: ``Chrispresso Inc.``" -msgstr "" +msgstr "Beispiel: ``Chrispresso Inc.``" #: ../channels/email/settings.rst:146 msgid "Option set to ``Agent Name``" -msgstr "" +msgstr "Einstellung auf ``Agenten-Name`` gesetzt" #: ../channels/email/settings.rst:140 msgid "Zammad will use the agent's name which is very personal." -msgstr "" +msgstr "Zammad verwendet dadurch den Agentenname, was persönlicher ist." #: ../channels/email/settings.rst:0 msgid "" "Usually you'd also want to remove the ticket slug from the subject in those " "cases." msgstr "" +"Vielleicht wollen Sie in diesem Fall auch die Ticket-Angabe im Betreff " +"entfernen." #: ../channels/email/settings.rst:0 msgid "Learn more in :doc:`Settings → Ticket `." msgstr "" +"Hier finden Sie weiter Infos :doc:`Einstellungen → Ticket `." #: ../channels/email/settings.rst:150 msgid "Sender Format Separator: Default value ``via``" -msgstr "" +msgstr "Sender Format Trenner. Standardwert: ``via``" #: ../channels/email/settings.rst:149 msgid "" "This is a can be a string you can freely choose. It divides the agent's name " "and the display name of the channel whenever needed." msgstr "" +"Das kann ein Text Ihrer Wahl sein. Dieser trennt den Name des Agenten und " +"der verwendeten E-Mail-Adresse einer Gruppe." #: ../channels/email/settings.rst:158 msgid "Ticket Subject Forward: Default value ``FWD``" -msgstr "" +msgstr "Ticket Betreff bei Weiterleitung. Standardwert: ``FWD``" #: ../channels/email/settings.rst:153 msgid "" "The above string will be used on the subject if you forward an email from " "Zammad." msgstr "" +"Die oben genannte Zeichenkette wird beim Weiterleiten einer E-Mail aus " +"Zammad verwendet." #: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 msgid "``:`` will be automatically appended to the above string." -msgstr "" +msgstr "``:`` wird der Zeichenkette automatisch angehängt." #: ../channels/email/settings.rst:166 msgid "Ticket Subject Reply: Default value ``RE``" -msgstr "" +msgstr "Ticket Betreff bei Antwort. Standardwert: ``RE``" #: ../channels/email/settings.rst:161 msgid "" "The above string will be used on the subject if you reply to a mail from " "Zammad." msgstr "" +"Die oben genannte Zeichenkette wird beim Beantworten einer E-Mail aus Zammad " +"verwendet." #: ../channels/email/settings.rst:180 msgid "Ticket Subject Size: Default value ``110``" -msgstr "" +msgstr "Ticket Betreff Größe. Standardwert: ``110``" #: ../channels/email/settings.rst:169 msgid "" @@ -2322,20 +2630,25 @@ msgid "" "truncate the length and insert ``[...]`` to show it has shortened the " "subject." msgstr "" +"Diese Einstellung erzwingt eine maximale Länge des Betreffs in E-Mails beim " +"Antworten. Falls der Betreff zu lang ist, wird Zammad diesen automatisch " +"abschneiden und ``[...]`` einfügen, um die Kürzung anzuzeigen." #: ../channels/email/settings.rst:174 msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" -msgstr "" +msgstr "Beispiel: ``RE: Test irgendw[...] [Ticket#123456]``" #: ../channels/email/settings.rst:178 msgid "" "This does **not** limit ticket titles within the UI, just the subjects when " "replying to an email." msgstr "" +"Das betrifft **nicht** den angezeigten Titel des Tickets in Zammad, sondern " +"nur den Betreff in E-Mails." #: ../channels/email/settings.rst:183 msgid "Enhanced settings" -msgstr "" +msgstr "Erweiterte Einstellungen" #: ../channels/email/settings.rst:185 msgid "" @@ -2344,32 +2657,43 @@ msgid "" "address for archiving reasons if needed. You can find the needed commands " "`within the advanced customization settings`_." msgstr "" +"Einige weniger wichtige Einstellungen können über die Rails console " +"vorgenommen werden, wenn benötigt. Beispielsweise kann Zammad alle " +"ausgehenden Mails per BCC an eine fixe E-Mail-Adresse schicken (z.B. zur " +"Archivierung). Sie können die dafür notwendigen Befehle :doc: `hier ` finden." #: ../channels/email/signatures.rst:2 msgid "Signatures" -msgstr "" +msgstr "Signaturen" #: ../channels/email/signatures.rst:8 msgid "" "You can create a separate signature for each group in Zammad. The individual " "signatures can be created and edited here." msgstr "" +"Sie können für jeden Gruppe in Zammad eine eigene Signatur erstellen. " +"Individuelle Signaturen können wir erstellt und bearbeitet werden." #: ../channels/email/signatures.rst:11 msgid "" "Afterwards, the existing (and active) signatures are available in the group " "editing mask:" msgstr "" +"Anschließend sind die erstellten und aktiven Signaturen in der " +"Gruppenbearbeitung verfügbar:" #: ../channels/email/signatures.rst:16 msgid "" "Each group can be assigned its own signature, but they can also all use the " "same signature." msgstr "" +"Jeder Gruppe kann eine eigene Signatur zugewiesen werden. Es kann aber auch " +"eine gemeinsame Signatur verwendet werden." #: ../channels/email/signatures.rst:21 msgid "Dynamic Signatures" -msgstr "" +msgstr "Dynamische Signaturen" #: ../channels/email/signatures.rst:23 msgid "" @@ -2380,6 +2704,11 @@ msgid "" "load a list of available variables, enter two colons (``::``) into the " "*Text* box of the signature editor." msgstr "" +"Um die Signaturen zu individualisieren, können Sie bestimmte Informationen " +"als :doc:`Variablen ` hinterlegen. Auf alle Informationen " +"eines Tickets, eines Kunden und eines Agenten kann hier zugegriffen werden. " +"Um eine Liste der verfügbaren Variablen zu sehen, geben Sie zwei " +"Doppelpunkte (``::``) in das Textfeld ein." #: ../channels/email/signatures.rst:32 msgid "" @@ -2388,12 +2717,18 @@ msgid "" "information are created with submitting the ticket and thus are not " "available before submitting." msgstr "" +"Bitte beachten Sie, dass manche Informationen bei der Erstellung des Tickets " +"noch nicht vorliegen. Ein gutes Beispiel hierfür ist die Ticketnummer. " +"Manche Attribute wie dieses werden erst mit der Erstellung des Tickets " +"gefüllt und sind deshalb erst nach dem Klick auf \"Erstellen\" verfügbar." #: ../channels/email/signatures.rst:40 msgid "" "Here is an example of a signature with variables and the result when you " "write a mail:" msgstr "" +"Hier ein Beispiel einer Signatur mit Variablen und dem zugehörigen Ergebnis " +"beim Verfassen:" #: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 msgid "Facebook" @@ -2404,80 +2739,100 @@ msgid "" "Please note that this part of our documentation currently is outdated. We " "currently are working on solutions for this topic." msgstr "" +"Bitte beachten Sie, dass dieser Teil der Dokumentation nicht mehr aktuell " +"ist. Wir arbeiten gerade an einer Lösung für dieses Problem." #: ../channels/facebook.rst:9 msgid "" "You can connect Facebook Accounts with Zammad. You need to connect your " "Zammad with Facebook first:" msgstr "" +"Sie können Ihre Facebook-Konten mit Zammad verbinden. Sie müssen dazu " +"zunächst Ihr Zammad mit Facebook verbinden:" #: ../channels/facebook.rst:12 msgid "For this start at: https://developers.facebook.com/apps/" -msgstr "" +msgstr "Gehen Sie dafür bitte auf: https://developers.facebook.com/apps/" #: ../channels/facebook.rst:18 msgid "Click on “Create App ID\" and enter app name" -msgstr "" +msgstr "Klicken Sie auf \"Create App ID\" und vergeben Sie einen Namen" #: ../channels/facebook.rst:39 msgid "***Configure Zammad as Facebook app***" -msgstr "" +msgstr "**Konfigurieren von Zammad als Facebook-App**" #: ../channels/facebook.rst:41 msgid "Go to “Admin -> Channels -> Facebook”" -msgstr "" +msgstr "Gehen Sie zu \"Einstellungen -> Kanäle -> Facebook\"" #: ../channels/facebook.rst:42 msgid "" "Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " "verify the “Callback URL”." msgstr "" +"Klicken Sie auf \"Facebook App verbinden\" und geben die Daten zu \"Facebook " +"App ID\" und \"Facebook-App-Zugangsdaten\" ein und prüfen die \"Callback URL" +"\"." #: ../channels/facebook.rst:45 msgid "Done, your Zammad is configured as Facebook App now." -msgstr "" +msgstr "Ihr Zammad ist nun als Facebook-App konfiguriert." #: ../channels/facebook.rst:48 msgid "***Link your Facebook Page to your Zammad Facebook app***" -msgstr "" +msgstr "**Verbinden Sie Ihre Facebook-Seite mit der Zammad Facebook-App**" #: ../channels/facebook.rst:50 msgid "" "Now you need to link your Facebook Page from which you want to get posts and " "send out comments." msgstr "" +"Nun müssen Sie Ihre Facebook-Seite verlinken, von der Sie Posts bekommen und " +"Kommentare abgeben wollen." #: ../channels/facebook.rst:53 msgid "" "Click on “Add Account”, then you will see the authorize app page of " "Facebook. Click on “authorize app”." msgstr "" +"Klicken Sie auf \"Add Account\"; anschließend werden Sie auf eine " +"Autorisierung-Seite von Facebook weitergeleitet. Klicken Sie auf \"authorize " +"app\"." #: ../channels/facebook.rst:60 msgid "" "You will get redirected back to Zammad. Now you need to configure your " "search keys, where mentions should get routed." msgstr "" +"Sie werden danach zurück zu Zammad geleitet. Nun müssen Sie " +"Schlüsselbegriffe definieren, mit denen Sie Erwähnungen steuern können." #: ../channels/facebook.rst:65 msgid "" "After you are done, you will get an overview of all linked Facebook Accounts." msgstr "" +"Anschließend bekommen Sie eine Übersicht über alle verbundenen Facebook-" +"Accounts angezeigt." #: ../channels/facebook.rst:70 msgid "***Start using your new channel***" -msgstr "" +msgstr "***Nutzen Sie Ihren neuen Kanal***" #: ../channels/facebook.rst:72 msgid "" "Start and write a post to your page, short time later you will have a new " "ticket in Zammad." msgstr "" +"Wenn Sie einen Post auf Ihrer Seite schreiben, sehen Sie kurze Zeit später " +"ein neues Ticket in Zammad." #: ../channels/facebook.rst:75 msgid "" "Just click on the reply button (as you do it for emails) to send a comment." msgstr "" +"Um einen Kommentar zu verfassen, klicken Sie auf den Antworten-Button (so " +"wie beim Antworten per E-Mail)." #: ../channels/form.rst:2 msgid "Forms" @@ -2490,10 +2845,15 @@ msgid "" "on. With Zammad it’s quite easy to integrate these forms into your website " "and directly generate tickets with them. In just 2 minutes." msgstr "" +"Feedback-/Kontaktformulare werden häufig auf Webseiten eingesetzt. " +"Üblicherweise werden daraus allerdings E-Mails generiert, die an einen " +"bestimmten Account geschickt und von dort weitergeleitet werden. Mit Zammad " +"können Sie in nur zwei Minuten ein solches Formular für Ihre Website " +"erstellen und Tickets generieren." #: ../channels/form.rst:None msgid "Zammad form management page" -msgstr "" +msgstr "Zammad Formular-Einstellungen" #: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 #: ../misc/object-conditions/basics.rst:12 @@ -2505,7 +2865,7 @@ msgstr "" #: ../system/integrations/ldap/index.rst:31 #: ../system/integrations/smime/prerequisites.rst:32 msgid "Limitations" -msgstr "Limitierungen" +msgstr "Einschränkungen" #: ../channels/form.rst:15 msgid "Please note the following limitations:" @@ -2513,53 +2873,58 @@ msgstr "Bitte beachten Sie die folgenden Limitierungen:" #: ../channels/form.rst:17 msgid "The fields provided by the form are limited to the following:" -msgstr "" +msgstr "Die im Formular nutzbaren Felder sind beschränkt auf die folgenden:" #: ../channels/form.rst:19 ../manage/groups/settings.rst:14 #: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 #: ../manage/templates.rst:33 msgid "Name" -msgstr "" +msgstr "Name" #: ../channels/form.rst:21 ../system/maintenance.rst:93 #: ../system/maintenance.rst:34 msgid "Message" -msgstr "" +msgstr "Nachricht" #: ../channels/form.rst:22 msgid "Attachment upload (optional)" -msgstr "" +msgstr "Hochladen von Anhängen (optional)" #: ../channels/form.rst:23 msgid "Checkbox for custom agreement text (optional)" -msgstr "" +msgstr "Checkbox für individuelle Hinweise (optional)" #: ../channels/form.rst:25 msgid "As of now only one dedicated form per instance is possible" -msgstr "" +msgstr "Aktuell kann nur ein Formular pro Instanz verwendet werden" #: ../channels/form.rst:30 msgid "Zammad comes with certain settings for forms." -msgstr "" +msgstr "Es gibt Einstellungen für Formulare in Zammad." #: ../channels/form.rst:39 ../manage/groups/settings.rst:102 #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:72 ../manage/templates.rst:43 #: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 msgid "Active" -msgstr "" +msgstr "Aktiv" #: ../channels/form.rst:33 msgid "" "By default the form channel is *inactive*. Use the switch in front of \"Form" "\" to activate this channel." msgstr "" +"Standardmäßig ist der Formular-Kanal *inaktiv*. Klicken Sie auf den Schalter " +"vor \"Formular\", um den Kanal zu aktivieren." #: ../channels/form.rst:38 msgid "" "Forms will not be displayed on your website if the channel is not active. " "This does not affect the form preview on the channels setting page." msgstr "" +"Formulare werden **nicht** auf Ihrer Webseite angezeigt, solange der Kanal " +"deaktiviert ist. Die Vorschau in den Formular-Einstellungen kann jedoch " +"immer angezeigt werden." #: ../channels/form.rst:43 msgid "Group selection for ticket creation" @@ -2570,10 +2935,12 @@ msgid "" "The group you set here defines where tickets should be created if they're " "supplied by Zammad's web form." msgstr "" +"Die Gruppenauswahl legt fest, in welcher Gruppe die über das Formular " +"kommenden Tickets erstellt werden sollen." #: ../channels/form.rst:46 msgid "Designer" -msgstr "" +msgstr "Designer" #: ../channels/form.rst:48 msgid "" @@ -2581,6 +2948,9 @@ msgid "" "you're happy with what you've chosen, you're provided with the code you need " "to copy to your website." msgstr "" +"In diesem Bereich können Sie das Formular anpassen. Sofern Sie mit dem " +"Ergebnis zufrieden sind müssen Sie den ausgegebenen Code noch in Ihrer " +"Website einfügen." #: ../channels/form.rst:54 msgid "" @@ -2588,34 +2958,41 @@ msgid "" "the provided source code needs to be copied every time you change settings " "here." msgstr "" +"Änderungen im Designer *werden nicht* in Zammad gespeichert. Das bedeutet, " +"dass Sie den Code nach jeder Änderung erneut kopieren und in Ihrer Webseite " +"einfügen müssen." #: ../channels/form.rst:None msgid "" "Zammad's form designer supports you with the initial configuration\n" "of your form." msgstr "" +"Der Formular-Designer von Zammad unterstützt Sie bei der initialen " +"Konfiguration Ihres Formulars." #: ../channels/form.rst:63 msgid "So let's talk about the options the designer provides." -msgstr "" +msgstr "Nun zu den möglichen Optionen im Designer." #: ../channels/form.rst:0 msgid "Title of the form" -msgstr "" +msgstr "Titel des Formulars" #: ../channels/form.rst:66 msgid "" "Choose how the heading of the form should be called. This setting is only " "relevant if you choose to display the form title in the form." msgstr "" +"Definieren Sie hier den Titel des Formulars. Diese Einstellung ist nur " +"relevant, wenn Sie die Option ``Titel im Formular anzeigen`` aktivieren." #: ../channels/form.rst:70 msgid "Default: ``Feedback Form``" -msgstr "" +msgstr "Standardwert: ``Feedback-Formular``" #: ../channels/form.rst:0 msgid "Name of form submit button" -msgstr "" +msgstr "Name für den Absende-Knopf" #: ../channels/form.rst:73 msgid "" @@ -2623,20 +3000,24 @@ msgid "" "provide your own wording with this option. It will be used every time the " "form is shown." msgstr "" +"Um die Beschriftung des \"Übermitteln-Buttons\" anzupassen können Sie hier " +"einen Freitext nach Ihrem Wunsch eingeben." #: ../channels/form.rst:0 msgid "Message after sending form" -msgstr "" +msgstr "Nachricht nach dem Versenden des Formulars" #: ../channels/form.rst:78 msgid "" "After your user pressed the submit button, they will be provided with a " "message containing the ticket number of the newly created ticket." msgstr "" +"Nachdem Ihre Benutzer den \"Übermitteln-Knopf\" geklickt haben, wird Ihnen " +"eine Nachricht mit der Ticketnummer angezeigt." #: ../channels/form.rst:81 msgid "Default *after* sending a form will look like so:" -msgstr "" +msgstr "Der Standardtext *nach* Übermitteln des Formulars sieht wie folgt aus:" #: ../channels/form.rst:0 msgid "Options" @@ -2646,34 +3027,39 @@ msgstr "Optionen" msgid "" "Zammad provides the following additional configuration options for your form." msgstr "" +"Zammad bietet Ihnen die folgenden zusätzlichen Konfigurationsmöglichkeiten." #: ../channels/form.rst:95 msgid "Enable debugging for implementation" -msgstr "" +msgstr "Debugging für Implementierung aktivieren" #: ../channels/form.rst:92 msgid "" "This option activates detailed debug information in your browser's developer " "tools console." msgstr "" +"Diese Option aktiviert detaillierte Debug-Informationen in der Entwickler-" +"Konsole Ihres Browsers." #: ../channels/form.rst:95 msgid "This option *should not* be active on productive forms!" -msgstr "" +msgstr "Diese Option *sollte nicht* in Produktivsystemen verwendet werden!" #: ../channels/form.rst:99 msgid "Show title in form" -msgstr "" +msgstr "Titel im Formular anzeigen" #: ../channels/form.rst:98 msgid "" "This setting belongs to the setting ``Title of the form`` and will provide " "the form title within the form dialogue if selected." msgstr "" +"Diese Einstellung hängt mit der Einstellung \"Titel des Formulars\" zusammen " +"und legt fest, ob ein Titel im Formular angezeigt wird." #: ../channels/form.rst:111 msgid "Start modal dialog for form" -msgstr "" +msgstr "Modal-Dialog für Formular starten" #: ../channels/form.rst:102 msgid "" @@ -2681,65 +3067,81 @@ msgid "" "selecting this option allows you to natively integrate the form within your " "website's body." msgstr "" +"Sofern ausgewählt, wird das Formular in einem Modal-Dialog beim Klick auf " +"einen Button geöffnet. Sofern die Option nicht ausgewählt ist, wird das " +"Formular innerhalb Ihrer Webseite eingebettet." #: ../channels/form.rst:106 msgid "This option is set by default." -msgstr "" +msgstr "Diese Einstellung ist standardmäßig aktiviert." #: ../channels/form.rst:110 msgid "" "No matter what you select here, the form *is always* loaded completely if " "your user browses the page containing the form." msgstr "" +"Unabhängig davon was Sie hier ausgewählt haben, wird das Formular *immer* " +"komplett geladen, wenn ein Benutzer die Seite direkt aufruft." #: ../channels/form.rst:118 msgid "" "Don't load CSS for the form You need to generate your own CSS for the form." msgstr "" +"Kein CSS für das Formular laden. Es muss eigenes CSS für das Formular " +"eingebunden werden." #: ../channels/form.rst:114 msgid "" "By default Zammad's form comes with basic CSS. This may not fit your " "website's design or even interfere with it." msgstr "" +"Standardmäßig ist ein CSS Basis-Design enthalten. Möglicherweise passt das " +"Design nicht zu dem Ihrer Website oder ist sogar störend." #: ../channels/form.rst:117 msgid "" "Selecting this option allows you to freely design the form without having to " "overwrite existing directives." msgstr "" +"Wenn Sie diese Option aktivieren, können Sie das Formular frei designen, " +"ohne das bestehende Design überschreiben zu müssen." #: ../channels/form.rst:131 msgid "Add attachment option to upload" -msgstr "" +msgstr "Hinzufügen einer Option für Anhänge" #: ../channels/form.rst:121 msgid "Allows your user to upload **one attachment** to the form." msgstr "" +"Erlaubt den Benutzern, **eine** Datei als Anhang zum Formular hochzuladen." #: ../channels/form.rst:123 msgid "**🤓 Watch allowed attachment sizes here**" -msgstr "" +msgstr "**🤓 Beachten Sie die erlaubte Größe für Anhänge**" #: ../channels/form.rst:125 msgid "" "This function *is not* limited technically. The only limitation that applies " "is your web servers upload limit." msgstr "" +"Diese Funktion ist technisch *nicht* begrenzt. Die einzige Begrenzung ist " +"das Größenlimit Ihres Webservers für Uploads." #: ../channels/form.rst:128 msgid "**SaaS only**" -msgstr "" +msgstr "**Ausschließlich SaaS**" #: ../channels/form.rst:130 msgid "" "If you're with Zammad hosted, attachments are limited by the package you've " "chosen." msgstr "" +"Sofern Ihr System bei Zammad gehostet wird, hängt das Größenlimit der " +"Anhänge von Ihrem gebuchten Paket ab." #: ../channels/form.rst:146 msgid "Add agreement text before submit" -msgstr "" +msgstr "Fügen Sie einen Bestätigungstext vor dem Absenden hinzu" #: ../channels/form.rst:134 msgid "" @@ -2748,22 +3150,31 @@ msgid "" "requirements, e.g. by providing data privacy notes that the user has to " "accept before submitting the form." msgstr "" +"Wenn diese Funktion aktiviert ist, können Sie einen Text definieren, den das " +"Formular zusammen mit einer Checkbox anzeigt. Dadurch können Sie " +"sicherstellen, dass das Formular Ihren (gesetzlichen) Anforderungen " +"entspricht und zum Beispiel eine Einwilligung zur Datenverarbeitung von " +"Nutzer einholen." #: ../channels/form.rst:0 msgid "" "Screencast showing a sample on how to configure the agreement\n" "text setting" -msgstr "" +msgstr "Screencast mit Beispiel zur Konfiguration eines Einverständnis-Felds" #: ../channels/form.rst:143 msgid "" "Zammad provides a free text form with limited capabilities. Use the *🔗 " "Weblink* button to add links to marked text passages." msgstr "" +"Zammad bietet ein Freitext-Formular mit eingeschränkten Funktionen. Benutzen " +"Sie den *🔗 Weblink* Button, um markierten Wörtern Links hinzuzufügen." #: ../channels/form.rst:146 msgid "This allows you to link e.g. to your data privacy or ToS information." msgstr "" +"Damit können Sie z.B. einen Link zu Ihrer Datenschutzerklärung oder Ihren " +"AGBs einfügen." #: ../channels/form.rst:149 ../manage/scheduler.rst:57 #: ../manage/slas/how-do-they-work.rst:37 @@ -2775,43 +3186,55 @@ msgid "" "Below the form options, Zammad provides a preview section to visualize the " "settings you've just chosen. By default you'll see a button named *Feedback*." msgstr "" +"Unter den Optionen für das Formular beinhaltet Zammad einen Vorschaubereich " +"des Formulars. Standardmäßig sehen Sie einen Button mit den Namen " +"**Feedback**." #: ../channels/form.rst:154 msgid "Clicking on the button will open the form modal." msgstr "" +"Wenn Sie auf diesen Button klicken, sehen Sie das Formular in einem " +"Dialogfenster." #: ../channels/form.rst:158 msgid "" "If the form channel is set to active, you already are able to create tickets " "even from this preview mode." msgstr "" +"Falls der Kanal aktiviert ist können Sie bereits Tickets über die Vorschau " +"des Formulars generieren." #: ../channels/form.rst:None msgid "Screenshot showing the preview section for the just configured form" -msgstr "" +msgstr "Screenshot mit Vorschau des konfigurierten Formulars" #: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 #: ../system/integrations/cti/placetel.rst:12 #: ../system/integrations/cti/sipgate.rst:12 #: ../system/integrations/zabbix.rst:10 msgid "Requirements" -msgstr "" +msgstr "Anforderungen" #: ../channels/form.rst:168 msgid "" "The requirement section provides you with everything you need in order to " "apply Zammad's web form to your website. It basically consists of two parts." msgstr "" +"Dieser Anforderungs-Bereich enthält alle notwendigen Schritte, um das " +"Webformular auf Ihrer Website einzurichten. Es sind grundsätzlich zwei Dinge " +"zu erledigen." #: ../channels/form.rst:0 msgid "Header section" -msgstr "" +msgstr "Header Bereich" #: ../channels/form.rst:172 msgid "" "The first code block provides you with Zammad's current jQuery dependency. " "This script section usually belongs to your website's header section." msgstr "" +"Der erste Code-Block enthält die jQuery Anforderung. Das Script wird " +"normalerweise im Header.Bereich Ihrer Website platziert." #: ../channels/form.rst:177 msgid "" @@ -2820,10 +3243,17 @@ msgid "" "your local requirements. You can use locally hosted jQuery version, " "**however** the version is fixed." msgstr "" +"Für das Formular wird folgendes Script-Tag vorgeschlagen, welches die " +"benötigten Javascript-Bibliothek von einer **externen Seite** lädt. Das kann " +"Ihren eigenen Anforderungen widersprechen. Sie können auch eine lokal " +"gehostete jQuery-Version nutzen, **allerdings muss die Version " +"übereinstimmen**." #: ../channels/form.rst:186 msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" +"Verwenden Sie nicht verschiedene jQuery-Versionen - die Wahrscheinlichkeit, " +"dass etwas nicht funktioniert ist hoch." #: ../channels/form.rst:0 msgid "Body section" @@ -2832,6 +3262,8 @@ msgstr "Body-Sektion" #: ../channels/form.rst:189 msgid "The second code block is the actual code required for your form to run." msgstr "" +"Der zweite Code-Block ist der Code, den das Formular benötigt um zu " +"funktionieren." #: ../channels/form.rst:191 msgid "" @@ -2839,18 +3271,25 @@ msgid "" "the settings selected above. This part belongs into the place you actually " "want the form or form button to appear." msgstr "" +"Die erste Zeile, welche ``id=\"zammad-feedback-form\"`` enthält, hängt stark " +"von den gewählten Konfiguration ab. Dieser Bereich gehört an die " +"entsprechende Stelle, wo das Formular erscheinen soll." #: ../channels/form.rst:195 msgid "" "The rest can either be placed at the same level or somewhere else on the " "same page." msgstr "" +"Der Rest kann ebenfalls dort oder irgendwo anders auf der selben Seite " +"eingefügt werden." #: ../channels/form.rst:200 msgid "" "This code block is updated automatically when changing settings in the " "designer above." msgstr "" +"Dieser Code-Block wird automatisch upgedatet, wenn Änderungen an den " +"Einstellungen im Formular-Designer vorgenommen werden." #: ../channels/form.rst:205 msgid "" @@ -2858,20 +3297,25 @@ msgid "" "your own website, you're on your own figuring out where exactly to place " "what." msgstr "" +"Diese Code-Statements hängen allerdings **stark** von Ihrer Website ab. Da " +"Sie selbst für Ihre Website verantwortlich sind, liegt es an Ihnen, die " +"genaue Implementierung in Erfahrung zu bringen und vorzunehmen." #: ../channels/form.rst:209 msgid "" "Take the Zammad website as an example, the embedded form version can look " "like the following if you apply custom CSS to it." msgstr "" +"Die Zammad Website dient als Beispiel, wie ein eingebettetes Formular mit " +"individuellem CSS aussehen kann." #: ../channels/form.rst:None msgid "Screenshot showing the zammad.com website with embedded web form" -msgstr "" +msgstr "Screenshot zeigt die Website zammad.com mit eingebettetem Formular" #: ../channels/form.rst:218 msgid "Potential Spam Issue" -msgstr "" +msgstr "Potenzielles Spam-Risiko" #: ../channels/form.rst:220 msgid "" @@ -2879,6 +3323,9 @@ msgid "" "tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " "them." msgstr "" +"Das Formular könnte missbraucht werden, um eine große Zahl an E-Mails zu " +"verschicken bzw. Tickets in Ihrer Zammad-Instanz zu generieren. Sofern Sie " +"das Formular nicht nutzen: **deaktivieren** Sie es." #: ../channels/form.rst:224 msgid "" @@ -2886,6 +3333,9 @@ msgid "" "based on different criteria. It also ensures that the email address being " "used is valid (with MX-Check on the email's domain)." msgstr "" +"Aber keine Sorge! Zammad begrenzt die Anzahl an erstellten Tickets auf Basis " +"verschiedener Kriterien. Außerdem stellt Zammad sicher, dass die verwendete " +"E-Mail-Adresse gültig ist (mittels MX-Check der E-Mail-Domain)." #: ../channels/form.rst:228 msgid "Form settings to limit ticket creation" @@ -2914,7 +3364,7 @@ msgstr "``20``" #: ../channels/form.rst:237 msgid "Limits ticket creation per IP and hour to 20 tickets" -msgstr "" +msgstr "Schränkt die Erstellung pro IP-Adresse und Stunde auf 20 Tickets ein" #: ../channels/form.rst:238 msgid "``form_ticket_create_by_ip_per_day``" @@ -2926,7 +3376,7 @@ msgstr "``240``" #: ../channels/form.rst:240 msgid "Limits ticket creation per IP and day to 240 tickets" -msgstr "" +msgstr "Schränkt die Erstellung pro IP-Adresse und Tag auf 240 Tickets ein" #: ../channels/form.rst:241 msgid "``form_ticket_create_per_day``" @@ -2939,34 +3389,41 @@ msgstr "``5000``" #: ../channels/form.rst:243 msgid "Limits ticket creation for forms to 5000 tickets per day" msgstr "" +"Schränkt die Erstellung durch ein Formular auf 5000 Tickets pro Tag ein" #: ../channels/form.rst:0 msgid "" "You can change these default values. Please keep in mind, that setting those " "values higher might lead to problems in term of created tickets." msgstr "" +"Sie können diese Standard-Werte anpassen. Bitte bedenken Sie, dass eine " +"Erhöhung ggf. Probleme in Sachen Ticketaufkommen verursacht." #: ../channels/form.rst:0 msgid "" "Please note that the following changes require console access to your Zammad " "host." msgstr "" +"Bitte beachten Sie, dass die folgenden Anpassungen Zugriff auf die Konsole " +"des Zammad-Hosts erfordern." #: ../channels/form.rst:253 msgid "**Change the ticket creation per IP and hour to 10**::" msgstr "" +"**Änderung der Ticketerstellung pro IP-Adresse und Stunde auf 10 Tickets**::" #: ../channels/form.rst:257 msgid "**Change the ticket creation per IP and hour to 50**::" msgstr "" +"**Änderung der Ticketerstellung pro IP-Adresse und Stunde auf 50 Tickets**::" #: ../channels/form.rst:261 msgid "**Change the ticket creation per day to 500**::" -msgstr "" +msgstr "**Änderung der Ticketerstellung pro Tag auf 500 Tickets**::" #: ../channels/form.rst:267 msgid "Further options to make it harder" -msgstr "" +msgstr "Weitere Maßnahmen, um Missbrauch zu erschweren" #: ../channels/form.rst:269 msgid "" @@ -2974,6 +3431,8 @@ msgid "" "instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" "form/form.js`` )." msgstr "" +"Als weitere Maßnahme, um Bots die Arbeit zu erschweren, können Sie den " +"Speicherort der ``form.js`` ( ``/opt/zammad/assets/form/form.js`` ) ändern." #: ../channels/form.rst:273 msgid "" @@ -2981,12 +3440,18 @@ msgid "" "copying) that you need to ensure that your ``form.js`` stays up to date if " "you update Zammad." msgstr "" +"Bitte beachten Sie, dass Sie beim Ändern des Verzeichnisses der ``form.js`` " +"(z.B. durch Kopieren) sicherstellen müssen, dass ``forms.js`` beim " +"Aktualisieren von Zammad ebenfalls auf Aktualisierung geprüft werden muss." #: ../channels/form.rst:277 msgid "" "It's not recommended to delete form.js from it's location in that case, but " "to forbid access to it via your web server configuration." msgstr "" +"In diesem Fall empfehlen wir nicht, ``forms.js`` vom ursprünglichen " +"Speicherort zu löschen, sondern den Zugriff über die Konfiguration Ihres " +"Webservers zu unterbinden." #: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 msgid ":doc:`accounts/register-app`" @@ -2997,26 +3462,29 @@ msgid "" "Use the **Connect Google App** dialog to register Zammad as an OAuth app on " "Google." msgstr "" +"Verwenden Sie den **Google App verbinden** Dialog, um Zammad als OAuth-App " +"in Google zu registrieren." #: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 msgid "(This step is **required**; read on to learn why.)" msgstr "" +"(Dieser Schritt ist **notwendig**; lesen Sie weiter, um zu erfahren warum.)" #: ../channels/google/accounts.rst:0 msgid "Registering Zammad as a Google OAuth app" -msgstr "" +msgstr "Registrieren von Zammad als eine Google OAuth-App" #: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 msgid "Use the **Add Account** dialog to connect your account." -msgstr "" +msgstr "Benutzen Sie den **Hinzufügen** Dialog, um das Konto hinzuzufügen." #: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 msgid "You're migrating existing email channels? Look below!" -msgstr "" +msgstr "Wollen Sie bestehende E-Mail-Kanäle migrieren? Lesen Sie unten weiter!" #: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 msgid "Adding your gmail account to Zammad" -msgstr "" +msgstr "Hinzufügen Ihres Gmail-Kontos zu Zammad" #: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 msgid ":doc:`accounts/migrate-from-email-channel`" @@ -4132,6 +4600,216 @@ msgstr "" "Kontaktieren Sie Ihre Administrator, falls Sie keinen Zugriff auf einen " "Administrator-Account haben." +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +#, fuzzy +#| msgid "Message" +msgid "Error message" +msgstr "Nachricht" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +#, fuzzy +#| msgid "Port" +msgid "or" +msgstr "Port" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +#, fuzzy +#| msgid "Personal accounts" +msgid "Private email account" +msgstr "Persönliche Accounts" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -4157,29 +4835,39 @@ msgstr "" msgid "Microsoft 365" msgstr "Microsoft 365" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +#, fuzzy +#| msgid ":doc:`Channels > Microsoft 365 `" +msgid ":doc:`🛟 Common M365 errors `" +msgstr ":doc:`Kanäle > Microsoft 365 `" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4324,267 +5012,382 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." msgstr "" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +#, fuzzy +#| msgid "Current User > Organization > Note" +msgid "Current situation" +msgstr "Aktueller Benutzer > Organisation > Notiz" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +#, fuzzy +#| msgid "Features" +msgid "Future" +msgstr "Features" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +#, fuzzy +#| msgid ":doc:`Channels > Twitter `" +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr ":doc:`Kanäle > Twitter `" + #: ../channels/web.rst:2 msgid "Web" msgstr "" @@ -5304,7 +6107,7 @@ msgstr "" #: ../manage/knowledge-base.rst:29 msgid "Features" -msgstr "Funktionen" +msgstr "Features" #: ../manage/knowledge-base.rst:31 msgid "🌍 Multi-language support" @@ -5875,15 +6678,15 @@ msgstr "relativ / 7 / Tage" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -5975,7 +6778,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -6072,11 +6875,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -6090,11 +6893,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -6667,7 +7470,7 @@ msgstr "" #: ../manage/public-links.rst:77 ../manage/public-links.rst:92 msgid "Login Screen" -msgstr "" +msgstr "Login" #: ../manage/public-links.rst:78 ../manage/public-links.rst:99 msgid "Signup Screen" @@ -7013,7 +7816,9 @@ msgid "``admin.channel_twitter``" msgstr "``admin.channel_twitter``" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +#, fuzzy +#| msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr ":doc:`Kanäle > Twitter `" #: ../manage/roles/admin-permissions.rst:84 @@ -9596,14 +10401,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "Benutzer" @@ -9619,67 +10416,95 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +#, fuzzy +#| msgid ":doc:`System > Integrations `" +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr ":doc:`System > Integrationen `" + +#: ../manage/users/index.rst:19 +#, fuzzy +#| msgid ":doc:`System > Integrations `" +msgid ":doc:`via Exchange integration `" +msgstr ":doc:`System > Integrationen `" + +#: ../manage/users/index.rst:20 +#, fuzzy +#| msgid "`System > API `_" +msgid "`via REST API `_" +msgstr "`System > API `_" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9689,13 +10514,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9703,25 +10528,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9729,54 +10554,54 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 #, fuzzy #| msgid "Organizations" msgid "🏤 Secondary Organizations" msgstr "Unternehmen" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "👑 VIP" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9788,39 +10613,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9828,29 +10653,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9861,18 +10686,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -12000,10 +12825,12 @@ msgstr "" #: ../misc/object-conditions/basics.rst:269 msgid "Click on a message to see detailed information about it." msgstr "" +"Klicken Sie direkt auf einen Ticket-Eintrag, um detaillierte Informationen " +"dazu zu erhalten." #: ../misc/object-conditions/basics.rst:0 msgid "Message details view" -msgstr "" +msgstr "Detailansicht der Nachricht" #: ../misc/object-conditions/basics.rst:0 msgid "What's the articles type (or not)?" @@ -14066,6 +14893,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "" + #: ../settings/security/third-party/twitter.rst:4 msgid "" "It is possible to create a quick login for your helpdesk via Twitter to do " @@ -19254,8 +20085,10 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" -msgstr "" +#, fuzzy +#| msgid ":doc:`Channels > Twitter `" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr ":doc:`Kanäle > Twitter `" #: ../system/objects/permissions.rst:32 msgid "SMS (incoming)" diff --git a/locale/es/LC_MESSAGES/admin-docs.po b/locale/es/LC_MESSAGES/admin-docs.po index 9c43a864..e92c6529 100644 --- a/locale/es/LC_MESSAGES/admin-docs.po +++ b/locale/es/LC_MESSAGES/admin-docs.po @@ -7,17 +7,18 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-05-04 16:53+0200\n" -"PO-Revision-Date: 2023-04-15 10:17+0000\n" -"Last-Translator: Jony \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: 2023-07-25 12:18+0000\n" +"Last-Translator: ERICK HERNANDEZ HERNANDEZ Ñ " +"\n" "Language-Team: Spanish \n" +"documentations/admin-documentation-latest/es/>\n" "Language: es\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" -"X-Generator: Weblate 4.16.4\n" +"X-Generator: Weblate 4.18.2\n" #: ../channels/chat.rst:2 msgid "Chat" @@ -472,21 +473,24 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:66 #: ../channels/email/accounts/secondary-addresses.rst:31 +#, fuzzy msgid "" "Email display names value can be :ref:`further customized in the Settings " "tab `." -msgstr "" +msgstr "ERICK HERNANDEZ HERNANDEZ" #: ../channels/email/accounts/account-setup.rst:77 #: ../channels/email/accounts/secondary-addresses.rst:35 #: ../channels/email/index.rst:2 ../channels/form.rst:20 #: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +#, fuzzy msgid "Email" -msgstr "" +msgstr "ERICK HERNANDEZ HERNANDEZ" #: ../channels/email/accounts/account-setup.rst:70 +#, fuzzy msgid "Your email address." -msgstr "" +msgstr "ERICK HERNANDEZ HERNANDEZ" #: ../channels/email/accounts/account-setup.rst:72 msgid "" @@ -4067,6 +4071,210 @@ msgid "" "Contact your administrator if you don’t have access to an admin account." msgstr "" +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -4092,29 +4300,37 @@ msgstr "" msgid "Microsoft 365" msgstr "" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4259,267 +4475,376 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" msgstr "" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + #: ../channels/web.rst:2 msgid "Web" msgstr "" @@ -5806,15 +6131,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -5902,7 +6227,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -5997,11 +6322,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -6015,11 +6340,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -6928,7 +7253,7 @@ msgid "``admin.channel_twitter``" msgstr "" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr "" #: ../manage/roles/admin-permissions.rst:84 @@ -9479,14 +9804,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "" @@ -9502,67 +9819,89 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9572,13 +9911,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9586,25 +9925,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9612,52 +9951,52 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9669,39 +10008,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9709,29 +10048,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9742,18 +10081,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13863,6 +14202,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "" + #: ../settings/security/third-party/twitter.rst:4 msgid "" "It is possible to create a quick login for your helpdesk via Twitter to do " @@ -19012,7 +19355,7 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" msgstr "" #: ../system/objects/permissions.rst:32 diff --git a/locale/es_CO/LC_MESSAGES/admin-docs.po b/locale/es_CO/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..ddb67e87 --- /dev/null +++ b/locale/es_CO/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22089 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: es_CO\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "" + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +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 +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 "🙅 The following attributes are **not customizable**:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +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:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" + +#: ../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/clearbit.rst:9 +msgid "Avatar" +msgstr "" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/integrations/i-doit.rst:2 +msgid "i-doit" +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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +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." +msgstr "" + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "" + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" + +#: ../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/es_MX/LC_MESSAGES/admin-docs.po b/locale/es_MX/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..891279ea --- /dev/null +++ b/locale/es_MX/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22089 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: es_MX\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "" + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +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 +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 "🙅 The following attributes are **not customizable**:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +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:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" + +#: ../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/clearbit.rst:9 +msgid "Avatar" +msgstr "" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/integrations/i-doit.rst:2 +msgid "i-doit" +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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +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." +msgstr "" + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "" + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" + +#: ../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/fa/LC_MESSAGES/admin-docs.po b/locale/fa/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..e561603d --- /dev/null +++ b/locale/fa/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22089 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: fa\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "" + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +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 +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 "🙅 The following attributes are **not customizable**:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +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:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" + +#: ../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/clearbit.rst:9 +msgid "Avatar" +msgstr "" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/integrations/i-doit.rst:2 +msgid "i-doit" +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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +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." +msgstr "" + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "" + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" + +#: ../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/fr/LC_MESSAGES/admin-docs.po b/locale/fr/LC_MESSAGES/admin-docs.po index 7d3a1de6..336468d9 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: 2023-05-04 16:53+0200\n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" "PO-Revision-Date: 2023-03-22 11:17+0000\n" "Last-Translator: Antoine Ducret \n" "Language-Team: French ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -4064,29 +4268,37 @@ msgstr "" msgid "Microsoft 365" msgstr "" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4231,267 +4443,382 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +#, fuzzy +#| msgid "Twitter" +msgid "Twitter/X" msgstr "Twitter" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +#, fuzzy +#| msgid "Twitter" +msgid "Twitter/X note" +msgstr "Twitter" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +#, fuzzy +#| msgid "Current User" +msgid "Current situation" +msgstr "Utilisateur courant" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + #: ../channels/web.rst:2 msgid "Web" msgstr "Web" @@ -5773,15 +6100,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -5869,7 +6196,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -5966,11 +6293,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -5984,11 +6311,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -6897,7 +7224,7 @@ msgid "``admin.channel_twitter``" msgstr "" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr "" #: ../manage/roles/admin-permissions.rst:84 @@ -9451,14 +9778,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "" @@ -9474,67 +9793,89 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9544,13 +9885,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9558,25 +9899,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9584,54 +9925,54 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 #, fuzzy #| msgid "Organizations" msgid "🏤 Secondary Organizations" msgstr "Sociétés" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9643,39 +9984,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9683,29 +10024,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9716,18 +10057,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13845,6 +14186,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "Twitter" + #: ../settings/security/third-party/twitter.rst:4 msgid "" "It is possible to create a quick login for your helpdesk via Twitter to do " @@ -18996,7 +19341,7 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" msgstr "" #: ../system/objects/permissions.rst:32 diff --git a/locale/fr_CA/LC_MESSAGES/admin-docs.po b/locale/fr_CA/LC_MESSAGES/admin-docs.po index 277800c7..f9401bf5 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: 2023-05-04 16:53+0200\n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" "PO-Revision-Date: 2021-12-03 14:33+0000\n" "Last-Translator: TRANSFER FROM TRANSIFEX \n" "Language-Team: French (Canada) ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -4200,29 +4404,37 @@ msgstr "" msgid "Microsoft 365" msgstr "" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4367,267 +4579,378 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" msgstr "" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +#, fuzzy +#| msgid "Ticket > Organization > Note" +msgid "Current situation" +msgstr "Billet > Organisation > Note" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + #: ../channels/web.rst:2 msgid "Web" msgstr "" @@ -5911,15 +6234,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -6009,7 +6332,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -6106,11 +6429,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -6124,11 +6447,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -7037,7 +7360,7 @@ msgid "``admin.channel_twitter``" msgstr "" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr "" #: ../manage/roles/admin-permissions.rst:84 @@ -9624,14 +9947,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "" @@ -9647,67 +9962,89 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9717,13 +10054,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9731,25 +10068,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9757,52 +10094,52 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9814,39 +10151,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9854,29 +10191,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9887,18 +10224,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -14050,6 +14387,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "" + #: ../settings/security/third-party/twitter.rst:4 msgid "" "It is possible to create a quick login for your helpdesk via Twitter to do " @@ -19315,7 +19656,7 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" msgstr "" #: ../system/objects/permissions.rst:32 diff --git a/locale/hr/LC_MESSAGES/admin-docs.po b/locale/hr/LC_MESSAGES/admin-docs.po index 443ea8bd..42a5502d 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: 2023-05-04 16:53+0200\n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" "PO-Revision-Date: 2022-06-15 13:40+0000\n" "Last-Translator: Ivan Perovic \n" "Language-Team: Croatian ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -4055,29 +4259,37 @@ msgstr "" msgid "Microsoft 365" msgstr "" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4222,267 +4434,376 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" msgstr "" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + #: ../channels/web.rst:2 msgid "Web" msgstr "" @@ -5764,15 +6085,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -5860,7 +6181,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -5955,11 +6276,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -5973,11 +6294,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -6886,7 +7207,7 @@ msgid "``admin.channel_twitter``" msgstr "" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr "" #: ../manage/roles/admin-permissions.rst:84 @@ -9437,14 +9758,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "" @@ -9460,67 +9773,89 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9530,13 +9865,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9544,25 +9879,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9570,52 +9905,52 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9627,39 +9962,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9667,29 +10002,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9700,18 +10035,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13813,6 +14148,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "" + #: ../settings/security/third-party/twitter.rst:4 msgid "" "It is possible to create a quick login for your helpdesk via Twitter to do " @@ -18958,7 +19297,7 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" msgstr "" #: ../system/objects/permissions.rst:32 diff --git a/locale/hu/LC_MESSAGES/admin-docs.po b/locale/hu/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..40eb465b --- /dev/null +++ b/locale/hu/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22089 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: hu\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "" + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +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 +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 "🙅 The following attributes are **not customizable**:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +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:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" + +#: ../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/clearbit.rst:9 +msgid "Avatar" +msgstr "" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/integrations/i-doit.rst:2 +msgid "i-doit" +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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +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." +msgstr "" + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "" + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" + +#: ../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/it/LC_MESSAGES/admin-docs.po b/locale/it/LC_MESSAGES/admin-docs.po index be860d3c..224ccc9a 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: 2023-05-04 16:53+0200\n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" "PO-Revision-Date: 2023-04-15 10:17+0000\n" "Last-Translator: crnfpp \n" "Language-Team: Italian ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -4004,29 +4208,37 @@ msgstr "" msgid "Microsoft 365" msgstr "" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4171,267 +4383,376 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" msgstr "" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + #: ../channels/web.rst:2 msgid "Web" msgstr "" @@ -5713,15 +6034,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -5809,7 +6130,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -5904,11 +6225,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -5922,11 +6243,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -6835,7 +7156,7 @@ msgid "``admin.channel_twitter``" msgstr "" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr "" #: ../manage/roles/admin-permissions.rst:84 @@ -9386,14 +9707,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "" @@ -9409,67 +9722,89 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9479,13 +9814,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9493,25 +9828,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9519,52 +9854,52 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9576,39 +9911,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9616,29 +9951,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9649,18 +9984,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13750,6 +14085,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "" + #: ../settings/security/third-party/twitter.rst:4 msgid "" "It is possible to create a quick login for your helpdesk via Twitter to do " @@ -18895,7 +19234,7 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" msgstr "" #: ../system/objects/permissions.rst:32 diff --git a/locale/nl/LC_MESSAGES/admin-docs.po b/locale/nl/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..74193ebb --- /dev/null +++ b/locale/nl/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22089 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: nl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "" + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +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 +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 "🙅 The following attributes are **not customizable**:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +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:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" + +#: ../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/clearbit.rst:9 +msgid "Avatar" +msgstr "" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/integrations/i-doit.rst:2 +msgid "i-doit" +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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +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." +msgstr "" + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "" + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" + +#: ../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/pl/LC_MESSAGES/admin-docs.po b/locale/pl/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..b5fc7f5e --- /dev/null +++ b/locale/pl/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22089 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: pl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "" + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +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 +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 "🙅 The following attributes are **not customizable**:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +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:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" + +#: ../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/clearbit.rst:9 +msgid "Avatar" +msgstr "" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/integrations/i-doit.rst:2 +msgid "i-doit" +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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +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." +msgstr "" + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "" + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" + +#: ../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/pt_BR/LC_MESSAGES/admin-docs.po b/locale/pt_BR/LC_MESSAGES/admin-docs.po index 2d26c01d..d8759b86 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: 2023-05-04 16:53+0200\n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" "PO-Revision-Date: 2022-08-01 14:09+0000\n" "Last-Translator: Erico Cesar \n" "Language-Team: Portuguese (Brazil) ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -4021,29 +4225,37 @@ msgstr "" msgid "Microsoft 365" msgstr "" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4206,267 +4418,378 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "A mensagen então aparecerá no seu cliente de Telegram." -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" msgstr "" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +#, fuzzy +#| msgid "Configure the integration" +msgid "Current situation" +msgstr "Configure a integração" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + #: ../channels/web.rst:2 msgid "Web" msgstr "Web" @@ -5799,15 +6122,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -5896,7 +6219,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -5993,11 +6316,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -6011,11 +6334,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -6929,7 +7252,7 @@ msgid "``admin.channel_twitter``" msgstr "" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr "" #: ../manage/roles/admin-permissions.rst:84 @@ -9525,14 +9848,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "Usuários" @@ -9548,67 +9863,89 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9618,13 +9955,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9632,25 +9969,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9658,54 +9995,54 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 #, fuzzy #| msgid "Organizations" msgid "🏤 Secondary Organizations" msgstr "Organizações" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9717,39 +10054,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9757,29 +10094,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9790,18 +10127,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13944,6 +14281,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "" + #: ../settings/security/third-party/twitter.rst:4 #, fuzzy msgid "" @@ -19146,7 +19487,7 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" msgstr "" #: ../system/objects/permissions.rst:32 diff --git a/locale/ru/LC_MESSAGES/admin-docs.po b/locale/ru/LC_MESSAGES/admin-docs.po index a30545dd..251bb9ac 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: 2023-05-04 16:53+0200\n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" "PO-Revision-Date: 2023-03-27 02:17+0000\n" "Last-Translator: MaDaRaUZzi \n" "Language-Team: Russian ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -3995,29 +4199,37 @@ msgstr "" msgid "Microsoft 365" msgstr "" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4162,267 +4374,376 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" msgstr "" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + #: ../channels/web.rst:2 msgid "Web" msgstr "" @@ -5702,15 +6023,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -5798,7 +6119,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -5893,11 +6214,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -5911,11 +6232,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -6824,7 +7145,7 @@ msgid "``admin.channel_twitter``" msgstr "" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr "" #: ../manage/roles/admin-permissions.rst:84 @@ -9375,14 +9696,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "" @@ -9398,67 +9711,89 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9468,13 +9803,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9482,25 +9817,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9508,52 +9843,52 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9565,39 +9900,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9605,29 +9940,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9638,18 +9973,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13737,6 +14072,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "" + #: ../settings/security/third-party/twitter.rst:4 msgid "" "It is possible to create a quick login for your helpdesk via Twitter to do " @@ -18882,7 +19221,7 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" msgstr "" #: ../system/objects/permissions.rst:32 diff --git a/locale/sr_Cyrl/LC_MESSAGES/admin-docs.po b/locale/sr_Cyrl/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..c4091900 --- /dev/null +++ b/locale/sr_Cyrl/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22098 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: 2023-08-10 07:56+0000\n" +"Last-Translator: Dusan Vuckovic \n" +"Language-Team: Serbian (cyrillic) \n" +"Language: sr_Cyrl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" +"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n" +"X-Generator: Weblate 4.18.2\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "Лозинка" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "Корисник" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "Решавање проблема" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "Атрибути тикета" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "Атрибути чланка" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "Група" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "Стање" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "Приоритет" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "Власник" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "Ограничења" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "Опис" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +#, fuzzy +#| msgid "Features" +msgid "Future" +msgstr "Функције" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "Групе" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "Заједнички нацрти" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "База знања" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "Функције" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "Тема" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "Наслов" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "Макрои" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "Макрои су **🖱 брзе пречице** за промене на тикета." + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "затворено" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "Ознаке" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "Организације" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "Прегледи" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "Зашто?" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "Страна за пријављивање" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "x" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "Календар" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "X" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "Обрачун времена" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "Клијент" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "Организација" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "Корисници" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "Стање" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "Кликните на поруку да бисте видели детаљне информације о њој." + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "Приказ детаља поруке" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "Брендинг" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +msgstr "Github" + +#: ../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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "Zammad" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "Обавештења" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "Радни токови" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "group" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +msgstr "власник" + +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" +msgstr "state" + +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "priority" + +#: ../system/integrations/checkmk/api-reference.rst:142 +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 "🙅 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 "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +msgstr "Checkmk" + +#: ../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/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" +"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" +msgstr "Аватар" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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 "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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "Icinga" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "Monit" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "Nagios" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +msgstr "S/MIME" + +#: ../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 "" +"S/MIME је најшире подржани метод за безбедну комуникацију путем имејла. Са S/" +"MIME, можете да размењујете **потписане** и **шифроване** поруке са другима." + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "Потписивање" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "Другим речима, гарантује **интегритет** и **аутентичност** поруке." + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "Шифровање" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "Снимак екрана са S/MIME функцијом за нове тикете и одговоре" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "Дугме ✅ **Потписивање** је онемогућено" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "Текст" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" + +#: ../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/sv/LC_MESSAGES/admin-docs.po b/locale/sv/LC_MESSAGES/admin-docs.po new file mode 100644 index 00000000..533b3a29 --- /dev/null +++ b/locale/sv/LC_MESSAGES/admin-docs.po @@ -0,0 +1,22089 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2012 - 2023, Zammad Foundation +# This file is distributed under the same license as the Zammad package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: Zammad\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: sv\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../channels/chat.rst:2 +msgid "Chat" +msgstr "" + +#: ../channels/chat.rst:4 +msgid "" +"Chat has gotten very important for company and overall customer support. If " +"used properly, support via chat can be a real efficiency booster. A downside " +"of chats is when nobody responds or a bot responding to the customer." +msgstr "" + +#: ../channels/chat.rst:9 +msgid "How to improve Support by Chat?" +msgstr "" + +#: ../channels/chat.rst:11 +msgid "" +"We've asked others about their opinion in our circles, to learn what people " +"expect or dislike. This is what we found out:" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Good experiences" +msgstr "" + +#: ../channels/chat.rst:16 +msgid "Getting personal support by a human being" +msgstr "" + +#: ../channels/chat.rst:17 +msgid "Getting a fast response" +msgstr "" + +#: ../channels/chat.rst:18 +msgid "Solving my problem quickly" +msgstr "" + +#: ../channels/chat.rst:26 +msgid "Bad experiences" +msgstr "" + +#: ../channels/chat.rst:21 +msgid "" +"A chat window on a website (while the chat being offline) with the hint to " +"\"Leave a message\"" +msgstr "" + +#: ../channels/chat.rst:23 +msgid "Long waiting queues before even writing with a personal" +msgstr "" + +#: ../channels/chat.rst:24 +msgid "" +"Receiving a message like \"My name is Nina, what can I do for you?\" after " +"sending a message with my issue." +msgstr "" + +#: ../channels/chat.rst:26 +msgid "A Chat that doesn't integrate itself into the Website properly" +msgstr "" + +#: ../channels/chat.rst:29 +msgid "Our answer: The Zammad Chat Widget" +msgstr "" + +#: ../channels/chat.rst:31 +msgid "" +"The task is clear: Work on the disadvantages of a regular support chat and " +"improve them." +msgstr "" + +#: ../channels/chat.rst:48 +msgid "Our approach is as follows" +msgstr "" + +#: ../channels/chat.rst:35 +msgid "" +"We'll only display the chat widget, if at least one agent is available and " +"the agent still has capacity." +msgstr "" + +#: ../channels/chat.rst:38 +msgid "" +"If no agent is online or the agents are absend, the chat won't be available" +msgstr "" + +#: ../channels/chat.rst:40 +msgid "" +"We're setting an agent as inactive, if the agent doesn't accept new chat " +"requests or the WebApp is offline. This way, your support staff can take " +"breaks without your customers waiting ages for a reaction (see point above)" +msgstr "" + +#: ../channels/chat.rst:43 +msgid "" +"Zammad does not respond to chat messages on it's own to ensure that there's " +"no strange delay coming afterwards. Zammad will fire a (configurable by " +"agent) auto response as soon as the agents accepts the Chat request." +msgstr "" + +#: ../channels/chat.rst:46 +msgid "" +"Zammad will try to adapt your main website colors to the chat. You can also " +"adjust those colors allowing you to integrate the chat into your website, " +"like it has been there before." +msgstr "" + +#: ../channels/chat.rst:51 +msgid "Configuration of the Chat widget" +msgstr "" + +#: ../channels/chat.rst:53 +msgid "" +"You can create chat widgets for your web pages to allow visitors to chat " +"with you." +msgstr "" + +#: ../channels/chat.rst:56 +msgid "" +"The area for configuring the chat can be found in the admin area at Channels " +"→ Chat:" +msgstr "" + +#: ../channels/chat.rst:61 +msgid "" +"You can set up chats for different websites and edit them independently. The " +"integrated designer helps the chat-widget to adapt to the website color. If " +"you don't like the proposed design, you can manually adjust the design. " +"Through the different previews you have the possibility to display directly " +"how the presentation looks on different devices." +msgstr "" + +#: ../channels/chat.rst:69 +msgid "**Usage**" +msgstr "" + +#: ../channels/chat.rst:71 +msgid "" +"Insert the widget code into the source code of every page on which you want " +"the chat to be visible on. It should be placed at the end of the page's " +"source code before the closing tag." +msgstr "" + +#: ../channels/chat.rst:77 +msgid "**Result**" +msgstr "" + +#: ../channels/chat.rst:79 +msgid "The final result will look like the following:" +msgstr "" + +#: ../channels/chat.rst:83 +msgid "**Requirements**" +msgstr "" + +#: ../channels/chat.rst:85 +msgid "" +"Zammad chat requires jQuery. If you don't already use it on your website " +"include it like this:" +msgstr "" + +#: ../channels/chat.rst:88 ../channels/form.rst:182 +msgid "" +"````" +msgstr "" + +#: ../channels/chat.rst:90 +msgid "You have two options to implement the chat on your website:" +msgstr "" + +#: ../channels/chat.rst:92 +msgid "Automatically show chat (that's the default-setting)" +msgstr "" + +#: ../channels/chat.rst:93 +msgid "or manually open chat." +msgstr "" + +#: ../channels/chat.rst:95 +msgid "**Chat restrictions**" +msgstr "" + +#: ../channels/chat.rst:97 +msgid "" +"You offer a chat for your target group, but you don't want to activate chat " +"for certain IP addresses or countries? Then you have the possibility to " +"block the wished IP addresses and countries fast and easily via the chat " +"configuration in the admin panel. The configuration panel looks like this:" +msgstr "" + +#: ../channels/chat.rst:104 +msgid "" +"You can also find more information about the chat customization in the admin " +"area." +msgstr "" + +#: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 +#: ../channels/microsoft365/accounts.rst:2 +msgid "Accounts" +msgstr "" + +#: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 +#: ../channels/microsoft365/accounts.rst:32 +msgid ":doc:`accounts/account-setup`" +msgstr "" + +#: ../channels/email/accounts.rst:13 +msgid "Use the **New Email Account** dialog to connect your account." +msgstr "" + +#: ../channels/email/accounts.rst:0 +msgid "New Email Account dialog" +msgstr "" + +#: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 +#: ../channels/microsoft365/accounts.rst:50 +msgid ":doc:`accounts/secondary-addresses`" +msgstr "" + +#: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 +#: ../channels/microsoft365/accounts.rst:44 +msgid "" +"Send and receive email at **additional email addresses**, all through the " +"same mailbox/account." +msgstr "" + +#: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 +#: ../channels/microsoft365/accounts.rst:58 +msgid ":doc:`accounts/managing-accounts`" +msgstr "" + +#: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 +#: ../channels/microsoft365/accounts.rst:53 +msgid "Edit the configuration of existing accounts in the **Accounts Panel**." +msgstr "" + +#: ../channels/email/accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.rst:None +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Existing accounts can be edited from the Accounts panel." +msgstr "" + +#: ../channels/email/accounts.rst:45 +msgid ":doc:`accounts/email-notification`" +msgstr "" + +#: ../channels/email/accounts.rst:40 +msgid "" +"Configure the outgoing mail provider for **system notifications**. (Self-" +"hosted installations only.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:2 +#: ../channels/google/accounts/account-setup.rst:2 +#: ../channels/microsoft365/accounts/account-setup.rst:2 +msgid "Account Setup" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:4 +msgid "Setting up a new email account? Here’s what all the settings do." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:6 +#: ../channels/google/accounts/account-setup.rst:8 +#: ../channels/microsoft365/accounts/account-setup.rst:7 +msgid "" +"☠️ **But first, a word of warning!** The import process does things you might " +"not expect:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:9 +#: ../channels/google/accounts/account-setup.rst:11 +#: ../channels/microsoft365/accounts/account-setup.rst:10 +msgid "" +"🚯 **Zammad will delete all emails in your inbox during the import process.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:12 +msgid "" +"Use the *Experts* dialog to :ref:`disable this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:19 +#: ../channels/google/accounts/account-setup.rst:17 +#: ../channels/microsoft365/accounts/account-setup.rst:16 +msgid "" +"📮 **Zammad will send an auto-reply message to every email it imports.** " +"(Including the old ones!)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:22 +msgid "" +"Use the *Experts* dialog to :ref:`change this behavior `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:31 +msgid "**Gmail / G Suite users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:28 +msgid "" +"Google is in the process of upgrading its security policies. To stay up-to-" +"date, do **not** add your account as an email channel — instead, create a :" +"doc:`Google channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:36 +msgid "**Microsoft 365 users:**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:34 +msgid "" +"Microsoft is in the process of upgrading its security policies. To stay up-" +"to-date, do **not** add your account as an email channel — instead, create " +"a :doc:`Microsoft 365 channel `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:40 +msgid "Basic" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:42 +msgid "" +"In most cases, Zammad is smart enough to figure out your email provider’s " +"configuration based on your email address alone." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"Enter your email address and password, and Zammad will figure out the\n" +"rest." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:67 +msgid "Organization & Department Name" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:53 +#: ../channels/email/accounts/secondary-addresses.rst:22 +msgid "The display name used for outgoing email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +#: ../channels/email/accounts/secondary-addresses.rst:0 +msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:60 +#: ../channels/email/accounts/secondary-addresses.rst:29 +msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:62 +msgid "" +"If you add :doc:`multiple addresses ` to a single " +"account, you can define a separate Organization & Department Name for each " +"one." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:66 +#: ../channels/email/accounts/secondary-addresses.rst:31 +msgid "" +"Email display names value can be :ref:`further customized in the Settings " +"tab `." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:77 +#: ../channels/email/accounts/secondary-addresses.rst:35 +#: ../channels/email/index.rst:2 ../channels/form.rst:20 +#: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 +msgid "Email" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:70 +msgid "Your email address." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:72 +msgid "" +"If your account login/username is different from your email address, use the " +"*Experts* dialog (see below)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:75 +msgid "" +"If your inbox receives mail for more than one email address, be sure to :doc:" +"`add your alternate addresses ` after account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:248 +#: ../channels/email/accounts/email-notification.rst:33 +#: ../settings/security/password.rst:2 +msgid "Password" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:80 +#: ../channels/email/accounts/account-setup.rst:127 +#: ../channels/email/accounts/account-setup.rst:246 +#: ../channels/email/accounts/email-notification.rst:33 +msgid "Your account password." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:87 +#: ../channels/email/accounts/managing-accounts.rst:26 +msgid "Destination Group" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:83 +msgid "" +"The :doc:`group ` that incoming mail will be assigned " +"to." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:86 +msgid "" +"Use :doc:`filters ` for more fine-grained sorting " +"of incoming email." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:92 +msgid "Experts" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:94 +msgid "" +"If Zammad can’t figure out how to connect your account (or if you just want " +"to access advanced settings), use the *Experts* dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "" +"When auto-detection fails, you will be presented with the \"Experts\"\n" +"account setup dialog." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:105 +msgid "Email Inbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:113 +#: ../system/objects/types.rst:128 +msgid "Type" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:108 +msgid "Choose from **IMAP** and **POP3**." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:110 +msgid "" +"In most cases, you want IMAP. (With POP3, you won’t be able to :ref:`keep " +"messages on the server ` or :ref:" +"`specify which folder to fetch from `.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "Host" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:116 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:118 +#: ../channels/email/accounts/account-setup.rst:149 +msgid "Contact your email provider or system administrator if you don’t know." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/email-notification.rst:30 +#: ../settings/security/third-party/microsoft.rst:72 +#: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 +msgid "User" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:121 +msgid "" +"This field is being pre-filled with your email address in case you've " +"provided one before opening the expert settings." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:124 +msgid "Adjust this setting in case your username and email address differ." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "SSL / STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:130 +msgid "Enable encryption when fetching messages." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:132 +msgid "You can choose from the following options:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:134 +msgid "No SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:138 +msgid "" +"Retrieving Emails, just like sending your username and password without any " +"encryption *is not secure*." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:141 +msgid "You should never use this configuration on internet machines!" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:143 +msgid "SSL" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:144 +msgid "STARTTLS" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:151 +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Port" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:147 +msgid "Your email server’s port (usu. ``993`` for IMAP, or ``995`` for POP3)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:173 +#: ../channels/google/accounts/account-setup.rst:76 +#: ../channels/microsoft365/accounts/account-setup.rst:138 +msgid "Folder" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:154 +msgid "" +"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:156 +msgid "" +"If specifying a nested folder, be sure to use the full path. (Some systems " +"use different **path separators**; *e.g.,* ``Inquiries/Tech-Support`` vs. " +"``Inquiries.Tech-Support``. Contact your email provider or system " +"administrator if you don’t know.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:161 +msgid "📥 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:163 +msgid "" +"In the last step of the account setup process, Zammad sends you an email " +"from your own account, then waits for it to appear in the folder specified " +"here. **Account verification will not complete until this test message has " +"been received.**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:169 +msgid "" +"If this folder does not receive incoming messages automatically, you may " +"have to manually check your inbox during the verification step and move " +"Zammad’s test message there when it arrives." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:197 +#: ../channels/google/accounts/account-setup.rst:98 +#: ../channels/microsoft365/accounts/account-setup.rst:160 +msgid "Keep messages on server" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:176 +#: ../channels/google/accounts/account-setup.rst:79 +#: ../channels/microsoft365/accounts/account-setup.rst:141 +msgid "Specify what happens to your emails after Zammad imports them:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:178 +#: ../channels/google/accounts/account-setup.rst:81 +#: ../channels/microsoft365/accounts/account-setup.rst:143 +msgid "``no`` Zammad deletes all imported messages" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:180 +#: ../channels/google/accounts/account-setup.rst:83 +#: ../channels/microsoft365/accounts/account-setup.rst:145 +msgid "``yes`` Zammad marks imported messages as read" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:182 +#: ../channels/google/accounts/account-setup.rst:85 +#: ../channels/microsoft365/accounts/account-setup.rst:147 +msgid "" +"(With this option, Zammad will only import unread messages. This means " +"Zammad may miss messages if the mailbox is externally modified.)" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:185 +#: ../channels/google/accounts/account-setup.rst:88 +#: ../channels/microsoft365/accounts/account-setup.rst:150 +msgid "🤔 **Why does Zammad delete messages by default?**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:187 +#: ../channels/google/accounts/account-setup.rst:90 +#: ../channels/microsoft365/accounts/account-setup.rst:152 +msgid "" +"If you never clean out your inbox, it’ll eventually reach its storage limit, " +"and your mail server will start **rejecting incoming messages**. Most Zammad " +"users never even look at their inbox once it’s set up, so they rely on " +"Zammad to keep it clean for them." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:193 +#: ../channels/google/accounts/account-setup.rst:96 +#: ../channels/microsoft365/accounts/account-setup.rst:158 +msgid "" +"If you choose **yes** here, remember that it’s your responsibility to clean " +"out your inbox from time to time to keep it below its storage limit." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:226 +msgid "Import as" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:0 +msgid "“Import as” option in email account setup dialog" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:205 +msgid "How should old emails be imported?" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:207 +msgid "" +"During the import process, Zammad treats **all messages** (including ones " +"you’ve already read from months or years ago) as if they had been sent " +"today: senders will receive auto-replies saying “your message has been " +"received and we’ll get back to you within 24 hours,” and tickets created for " +"each message will be marked as “new”." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:214 +msgid "" +"Use this option to disable this behavior for messages more than two weeks " +"old." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:217 +msgid "This option may not be shown if:" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:219 +msgid "all messages in your inbox are less than two weeks old" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:220 +msgid "you selected **Keep messages on server: Yes**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:221 +msgid "you selected **Type: POP3**" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:223 +msgid "" +"For more fine-grained control, manually disable this and other :doc:" +"`triggers ` before adding an email account, then turn them " +"back on once all your messages have been imported." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:229 +msgid "Email Outbound" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:235 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Send mails via" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:232 +#: ../channels/email/accounts/email-notification.rst:21 +msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:234 +msgid "" +"Local MTA (mail transfer agent) configuration is only available on self-" +"hosted installations." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:238 +#: ../channels/email/accounts/email-notification.rst:24 +msgid "" +"Your email server’s hostname or IP address (*e.g.,* ``smtp.gmail.com``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:241 +#: ../channels/email/accounts/email-notification.rst:27 +msgid "Your account login/username." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:243 +#: ../channels/email/accounts/account-setup.rst:248 +msgid "Leave blank to use the same value from incoming account setup." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:251 +#: ../channels/email/accounts/email-notification.rst:36 +msgid "Your email server’s port (usu. ``587`` or ``465``)." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:253 +#: ../channels/email/accounts/email-notification.rst:38 +msgid "Zammad will detect and enable SSL/STARTTLS support automatically." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:256 +msgid "Verification" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:None +msgid "Email account verification step" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:262 +msgid "" +"As a final step, Zammad sends a test email from your own account, to your " +"own account, and to ``verify-external-smtp-sending@discard.zammad.org`` " +"which discards the test mail right away." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:266 +msgid "" +"We've created a `landing page for discard.zammad.org`_ which describes the " +"backgrounds as well." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:272 +msgid "" +"This this Zammad ensures that your email account is capable of sending " +"internal and external - once this is verified the setup process is complete! " +"🎉" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:1 +msgid "🤓 **Don't forget to set the outgoing email address**" +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:3 +msgid "" +"In Zammad each group decides about the email address that's used for " +"outgoing emails. The incoming group technically has no effect on it." +msgstr "" + +#: ../channels/email/accounts/account-setup-group-hint.include.rst:6 +msgid "" +"For this reason make sure to also adjust each affected :doc:`groups setting " +"`." +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:278 +#: ../channels/google/accounts/account-setup.rst:116 +#: ../channels/google/accounts/register-app.rst:116 +#: ../channels/microsoft365/accounts/account-setup.rst:178 +#: ../settings/security/third-party/saml.rst:156 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:2 +#: ../system/integrations/github.rst:57 ../system/integrations/gitlab.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:2 +msgid "Troubleshooting" +msgstr "" + +#: ../channels/email/accounts/account-setup.rst:280 +msgid "" +":ref:`Is a custom incoming mail folder to blame? `" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:2 +msgid "Email Notification" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:4 +msgid "" +"The notification channel can only be configured on **self-hosted " +"installations**." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:7 +msgid "For more information, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:9 +#: ../manage/trigger/system-notifications.rst:7 +msgid "" +"System notifications are automated emails sent by Zammad for critical system " +"events, such as account changes or SLA violations." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:13 +msgid "" +"Use the **Email Notification** panel to configure how Zammad dispatches " +"these notifications." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:None +msgid "Demonstration of email notification channel editing" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:29 +msgid "" +"The “From:” address on system notifications can be configured under :doc:" +"`Channels > Email > Settings > Notification Sender <../settings>`." +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:40 +msgid "🤔 **This looks familiar... Where have I seen it before?**" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:42 +msgid "This configuration step was part of the Getting Started wizard:" +msgstr "" + +#: ../channels/email/accounts/email-notification.rst:0 +msgid "" +"The getting started wizard asking how one wants to send out\n" +"notifications" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:2 +msgid "Managing Accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:4 +msgid "" +"Once an account has been added, use the Accounts panel to edit its " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:14 +msgid "Mail Server Settings" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound/outbound account details to change your server " +"configuration." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:0 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:0 +msgid "Location of account details settings for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:15 +msgid "⌨️ In some browsers, you may have to manually re-enter your password." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:14 +msgid "Click on the group name to reassign the account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/google/accounts/account-setup.rst:0 +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Location of \"Destination Group\" setting for existing accounts" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:21 +#: ../channels/google/accounts/account-setup.rst:109 +#: ../channels/microsoft365/accounts/account-setup.rst:171 +msgid "Only **active** groups will be displayed." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:23 +#: ../channels/google/accounts/account-setup.rst:111 +#: ../channels/microsoft365/accounts/account-setup.rst:173 +msgid "" +"Changing this setting will not reassign existing tickets to the new group." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:25 +msgid "" +"📮 **Still can’t send outgoing email tickets?** Check your :doc:`group " +"settings `." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:37 +msgid "Email Address" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:29 +msgid "" +"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this " +"account." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:32 +msgid "" +"See :doc:`secondary-addresses` for a detailed description of each option." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +msgid "Location of email address add/edit buttons" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "Enabled / Disabled" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:40 +msgid "" +"Disabling an account temporarily prevents Zammad from importing its messages." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:42 +msgid "" +"This may be necessary during scheduled maintenance or when migrating your " +"installation to a new host." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:47 +msgid "📮 Disabling an account disables *outgoing* messages for it, as well." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:51 +#: ../channels/email/accounts/managing-accounts.rst:52 +#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:163 +#: ../manage/knowledge-base.rst:195 +msgid "Delete" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:50 +msgid "Deleting an account removes its configuration from Zammad entirely." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:1 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:1 +msgid "🧹 **Additional Steps Required**" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"When an email account is deleted, its :doc:`email aliases ` **remain in the system**. Be sure to reassign or delete them " +"manually." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.rst:0 +#: ../channels/email/accounts/managing-accounts.delete-note.rst:0 +msgid "List of orphaned email addresses" +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:12 +msgid "" +"Click on the address to assign it to another account, or click ✖ to delete " +"it." +msgstr "" + +#: ../channels/email/accounts/managing-accounts.delete-note.rst:15 +#: ../channels/google/accounts/managing-accounts.delete-note.rst:3 +#: ../channels/microsoft365/accounts/managing-accounts.delete-note.rst:3 +msgid "" +"Groups need an assigned an address to send outgoing emails. If you delete a " +"group’s assigned address, agents belonging to that group won’t be able to " +"send emails until you assign it a new one." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:2 +msgid "Secondary Addresses" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:4 +msgid "" +"Secondary addresses (also known as *aliases*) allow you to send emails with " +"a different “From:” address from the one on the account." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Video demonstration of adding a secondary address and configuring\n" +"a group to use it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:12 +msgid "" +"Once you add a secondary address, you can configure a group to start sending " +"emails with it." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:1 +msgid "🙅 **Do not abuse this feature.**" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.warning.rst:3 +msgid "" +"If you use secondary addresses to impersonate other parties, your IP is " +"liable to get added to a spam blacklist." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:17 +msgid "" +"Your email provider may also be set up to *receive incoming messages* for " +"many addresses in the same mailbox. If this is the case, be sure to add your " +"alternate inbox addresses here." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:32 +msgid "Display Name" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:35 +msgid "The alias address to send outgoing messages as." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +#: ../channels/google/accounts/account-setup.rst:60 +#: ../channels/microsoft365/accounts/account-setup.rst:122 +msgid "Channel" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:38 +msgid "" +"The email account to be used when sending outgoing messages from this alias." +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +#: ../channels/email/accounts/secondary-addresses.rst:42 +#: ../manage/groups/settings.rst:86 ../manage/macros/how-do-they-work.rst:0 +#: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:69 +#: ../manage/webhook/add.rst:118 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:10 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +msgid "Note" +msgstr "" + +#: ../channels/email/accounts/secondary-addresses.rst:41 +msgid "" +"Optional. Only visible from this dialog, the REST API, and the Rails console." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:2 +msgid "Watch your inbox with Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:4 +msgid "Maybe you want to add emails via Fetchmail or Procmail to Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:6 +msgid "To get this to work you need to pipe your emails to rails." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:10 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` below. To learn more, see " +"`Administration via Console `_." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:15 +msgid "**Command line**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:23 +msgid "Fetchmail" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:25 +msgid "**Create .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:33 +#: ../channels/email/advanced/fetchmail.rst:53 +msgid "**vi .fetchmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:41 +msgid "That's it. Emails now will be directly piped into Zammad." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:46 +msgid "Using Procmail for advanced features like presorting" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:48 +msgid "" +"If you want to do some more with your emails, like presorting to a Zammad " +"group or filtering spam, you can use Procmail." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:51 +msgid "Fetchmail config looks slightly different." +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:61 +msgid "**Create .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/fetchmail.rst:67 +msgid "**vi .procmailrc**::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:2 +msgid "Dispatch messages with Sendmail" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:6 +msgid "" +"For the initial setup of this you need administrative rights on the Zammad " +"machine (console)." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:9 +msgid "" +"If you try to configure **only** an outgoing email account (as in, you do " +"not wish to set up an incoming IMAP/POP3 account at all), you will find that " +"it’s simply not possible via the email channel setup wizard. Instead, you " +"will have to create it via the CLI." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:14 +msgid "" +"(The wizard is designed to provide an idiot-proof email configuration " +"process for the average, non-technical user, so certain advanced options and " +"use cases have been deliberately omitted.)" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:18 +msgid "" +"To configure Zammad to use sendmail, run the following command (you can use " +"rails r [...] if you installed Zammad from source)::" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:23 +msgid "" +"Now, you should see a new **Email Account** entry in the admin settings " +"panel:" +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"The new, outbound-only email channel appears in the admin settings\n" +"email panel." +msgstr "" + +#: ../channels/email/advanced/sendmail.rst:30 +msgid "" +"Use the **Add** button under the **Email Address** heading to add new email " +"addresses to send from." +msgstr "" + +#: ../channels/email/email-headers.rst:2 +msgid "Email header manipulation" +msgstr "" + +#: ../channels/email/email-headers.rst:4 +msgid "" +"Email header manipulation allows you to re-route or adjust tickets apart " +"from filters or triggers. Like an API call, but with emails." +msgstr "" + +#: ../channels/email/email-headers.rst:7 +msgid "Header checks are case insensitive." +msgstr "" + +#: ../channels/email/email-headers.rst:9 +msgid "**🛡 Trusted channels required 🛡**" +msgstr "" + +#: ../channels/email/email-headers.rst:11 +msgid "" +"Below options are a potential risk with external communication and thus " +"require channels being set to trusted explicitly." +msgstr "" + +#: ../channels/email/email-headers.rst:16 +msgid "" +"Below headers are examples and –in our opinion– the most relevant ones. " +"However: You can adjust mostly any article or ticket attribute (yes, custom " +"ones as well) if you know the attribute's exact name." +msgstr "" + +#: ../channels/email/email-headers.rst:20 +msgid "" +"The name column within :doc:`object's management ` provides " +"easy access to objects attribute names. 🤓" +msgstr "" + +#: ../channels/email/email-headers.rst:24 +msgid "Trigger auto responses" +msgstr "" + +#: ../channels/email/email-headers.rst:26 +msgid "" +"Normally Zammad runs internal checks to see if an email is an automatic " +"response. In these cases Zammad will not send trigger based responses." +msgstr "" + +#: ../channels/email/email-headers.rst:29 +msgid "" +"There may be use cases where this behavior may be in your way, below options " +"allow you to overcome this issue." +msgstr "" + +#: ../channels/email/email-headers.rst:34 +msgid "" +"In some cases combining below headers is crucial. This is intentional but " +"may be confusing." +msgstr "" + +#: ../channels/email/email-headers.rst:44 +msgid "``x-zammad-send-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:38 +msgid "" +"Set to ``false`` to disable trigger based responses. If set to ``true`` " +"Zammad will send a response." +msgstr "" + +#: ../channels/email/email-headers.rst:43 +msgid "" +"This option *does not* work if e.g. ``precedence: list`` is set unless you " +"use below auto response header as well." +msgstr "" + +#: ../channels/email/email-headers.rst:56 +msgid "``x-zammad-is-auto-response``" +msgstr "" + +#: ../channels/email/email-headers.rst:47 +msgid "" +"Providing this header allows you to tell Zammad that the mail in question is " +"an auto generated response (``true``). This will cause email based triggers " +"to be skipped." +msgstr "" + +#: ../channels/email/email-headers.rst:51 +msgid "Set this header to ``false`` if you want to generate auto responses." +msgstr "" + +#: ../channels/email/email-headers.rst:55 +msgid "" +"This header allows you to overwrite auto detects for e.g. ``precedence: " +"list``." +msgstr "" + +#: ../channels/email/email-headers.rst:59 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:61 +msgid "" +"Zammad allows you to use headers to manipulate ticket creations or follow " +"ups. The manipulation can be used instead of triggers. Triggers are " +"considered *after* header settings and thus can still overrule." +msgstr "" + +#: ../channels/email/email-headers.rst:65 +msgid "**🔎 Zammad differentiates between ticket creation and follow up**" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``" +msgstr "" + +#: ../channels/email/email-headers.rst:70 +msgid "" +"This allows you to ensure the changes are only applied in the required " +"situation." +msgstr "" + +#: ../channels/email/email-headers.rst:73 +msgid "**🧐 About values**" +msgstr "" + +#: ../channels/email/email-headers.rst:75 +msgid "" +"While headers are not case sensitive, values like e.g. priority names are " +"case censitive: ``1 low`` will work, but ``1 lOw`` will not!" +msgstr "" + +#: ../channels/email/email-headers.rst:77 +msgid "" +"When using attributes that require date / time values, ensure to use Time " +"Zoned Times. e.g. for 28th September 2021 on 8 am CEST, either use:" +msgstr "" + +#: ../channels/email/email-headers.rst:80 +msgid "``2021-09-28T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:81 +msgid "``2021-09-28T08:00:00+02:00``" +msgstr "" + +#: ../channels/email/email-headers.rst:82 +msgid "``2021-09-28T06:00:00.000Z``" +msgstr "" + +#: ../channels/email/email-headers.rst:86 +msgid "``X-Zammad-Ticket-Priority`` & ``X-Zammad-Ticket-FollowUp-Priority``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you to adjust a ticket's priority." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Priority: 1 low``" +msgstr "" + +#: ../channels/email/email-headers.rst:90 +msgid "``X-Zammad-Ticket-Group`` & ``X-Zammad-Ticket-FollowUp-Group``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Allows you interfere with regular channel routing of the ticket." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Group: Sales``" +msgstr "" + +#: ../channels/email/email-headers.rst:95 +msgid "``X-Zammad-Ticket-Owner`` & ``X-Zammad-Ticket-FollowUp-Owner``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Directly assign or change the ticket owner. Valid values are either " +"``login`` or ``Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-Owner: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:105 +msgid "``X-Zammad-Ticket-State`` & ``X-Zammad-Ticket-FollowUp-State``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Set a specific ticket state." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ticket-State: closed``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Pending states always require the ``pending_time`` attribute on top." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Like so: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +msgid "``X-Zammad-Customer-Email``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Manipulate the ticket customer - this can be a different user than the " +"actual sender. Replying to the original sender is still possible." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Email: jdoe@example.com``" +msgstr "" + +#: ../channels/email/email-headers.rst:114 +#: ../channels/email/email-headers.rst:123 +msgid "This header is not available for follow ups." +msgstr "" + +#: ../channels/email/email-headers.rst:123 +msgid "``X-Zammad-Customer-Login``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Customer-Login: jdoe``" +msgstr "" + +#: ../channels/email/email-headers.rst:126 +msgid "Article attributes" +msgstr "" + +#: ../channels/email/email-headers.rst:128 +msgid "" +"If needed Zammad allows you to manipulate attributes or states of fetched " +"email articles." +msgstr "" + +#: ../channels/email/email-headers.rst:142 +msgid "``X-Zammad-Article-Sender``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the sender type (Agent, Customer, or System)" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Sender: System``" +msgstr "" + +#: ../channels/email/email-headers.rst:137 +msgid "" +"System Emails are indicated in a similar way as trigger-response like " +"entries Users can't see them natively." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Received mail as article sender system" +msgstr "" + +#: ../channels/email/email-headers.rst:152 +msgid "``X-Zammad-Article-Type``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "" +"Change the article type of your incoming mail. This requires you to know " +"which article types are available in your system." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Type: phone``" +msgstr "" + +#: ../channels/email/email-headers.rst:151 +msgid "" +"This header can cause *serious issues* in your instance and may lead to " +"unexpected behavior. Only use with absolute care!" +msgstr "" + +#: ../channels/email/email-headers.rst:156 +msgid "``X-Zammad-Article-Internal``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Manipulate the default article visibility." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Article-Internal: true``" +msgstr "" + +#: ../channels/email/email-headers.rst:159 +#: ../channels/email/email-headers.rst:160 +msgid "``X-Zammad-Ignore``" +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Tell Zammad to silently drop the Email." +msgstr "" + +#: ../channels/email/email-headers.rst:0 +msgid "Example: ``X-Zammad-Ignore: true``" +msgstr "" + +#: ../channels/email/filters.rst:2 +msgid "Filters" +msgstr "" + +#: ../channels/email/filters.rst:None ../channels/email/settings.rst:None +#: ../channels/email/signatures.rst:None +msgid "Account settings page" +msgstr "" + +#: ../channels/email/filters.rst:13 +msgid "" +"Postmaster filters allow you to match email headers (e.g. ``From``, ``To``, " +"``Subject``, ``X-Spam-Flag`` etc.) and execute a set of actions whenever " +"Zammad's email parser encounters a matching email. The actions will be " +"applied to the ticket that is created or updated by this email." +msgstr "" + +#: ../channels/email/filters.rst:18 +msgid "" +"Zammad comes with system filters as well. While you can't change them, it " +"might be useful for you what they actually do. Learn more on :doc:`filters/" +"system-filters`" +msgstr "" + +#: ../channels/email/filters.rst:22 +msgid "Here are some examples of what is possible with filters:" +msgstr "" + +#: ../channels/email/filters.rst:35 +msgid "Automatically dispatch tickets into certain groups:" +msgstr "" + +#: ../channels/email/filters.rst:25 +msgid "" +"For example, tickets from ``amazon.com`` could automatically be dispatched " +"to the Purchasing group." +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``regex:(\\.|@)amazon\\.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Group: Purchasing" +msgstr "" + +#: ../channels/email/filters.rst:33 +msgid "" +"Note that the Group action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the group of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:45 +msgid "Automatically increase the priority of tickets from a VIP customer:" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "From: contains: ``ourvipcustomer@example.com``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Priority: 3 high" +msgstr "" + +#: ../channels/email/filters.rst:43 +msgid "" +"Note that the Priority action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the priority of existing " +"tickets." +msgstr "" + +#: ../channels/email/filters.rst:57 +msgid "" +"Automatically tag and close spam tickets that have been marked as spam by " +"anexternal spam filter (e.g. SpamAssassin):" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "X-Spam-Flag: contains: ``YES``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "Tag: add: ``spam``" +msgstr "" + +#: ../channels/email/filters.rst:0 +msgid "State: closed" +msgstr "" + +#: ../channels/email/filters.rst:54 +msgid "" +"Note that the State action only has an effect when the matching email " +"results in a new ticket. Zammad will not change the state of existing " +"tickets. It will add the tag though if it missing, even if the mail is an " +"update to an existing ticket." +msgstr "" + +#: ../channels/email/filters.rst:59 +msgid "The following actions are only effective when creating tickets:" +msgstr "" + +#: ../channels/email/filters.rst:61 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +#: ../system/objects/permissions.rst:55 +msgid "Group" +msgstr "" + +#: ../channels/email/filters.rst:62 ../manage/macros/learn-by-example.rst:0 +msgid "State" +msgstr "" + +#: ../channels/email/filters.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:197 +msgid "Priority" +msgstr "" + +#: ../channels/email/filters.rst:64 ../manage/macros/learn-by-example.rst:0 +msgid "Owner" +msgstr "" + +#: ../channels/email/filters.rst:66 +msgid "" +"Different attributes of a filter can be combined with each other. Likewise, " +"the following actions can be combined. The supported matches are \"contains" +"\" and \"contains not\"; for advanced matching, you can use regular " +"expressions by prefixing the string with ``regex:``." +msgstr "" + +#: ../channels/email/filters.rst:71 +msgid "" +"Note that Zammad matches against the full header, e.g. for a mail with " +"``From: Display Name ``, the ``From`` condition " +"will test against ``Display Name ``. This is " +"especially important when using anchored regular expressions; ``regex:" +"^display\\.name@example.com$`` would not match this mail!" +msgstr "" + +#: ../channels/email/filters.rst:77 +msgid "" +"It should be borne in mind that the combined attributes build on each other. " +"If a filter is no longer needed, it can either be temporarily set inactive " +"or deleted directly." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:2 +msgid "System Filters" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:4 +msgid "" +"On this page you can find some pre-defined filters that you won't find " +"within the Zammad's UI. Those filters might come in handy when trying to " +"understand Zammad's behavior." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:10 +msgid "" +"Please note that this is not a full filters list, if you're missing filters, " +"feel free to ask over at the `Community`_." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:16 +msgid "JIRA" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:18 +msgid "" +"Zammad will detect Service Now emails and assign them to existing tickets, " +"if the following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:21 +msgid "Headers contain the ``X-ServiceNow-Generated`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:22 +msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:24 +msgid "See `JIRA Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:27 +msgid "Service-Now" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:29 +msgid "" +"Zammad will detect JIRA emails and assign them to existing tickets, if the " +"following requirements are met:" +msgstr "" + +#: ../channels/email/filters/system-filters.rst:32 +msgid "Headers contain the ``X-JIRA-FingerPrint`` header." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:33 +msgid "" +"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. " +"``[JIRA] (SYS-422)``." +msgstr "" + +#: ../channels/email/filters/system-filters.rst:36 +msgid "See `Service-Now Mail Example`_ for comparison of your emails." +msgstr "" + +#: ../channels/email/index.rst:13 +msgid "Control how Zammad **sends and receives email**." +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "**Using Gmail / G Suite?**" +msgstr "" + +#: ../channels/email/index.rst:18 +msgid "Set up a :doc:`Google channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "**Using Microsoft 365?**" +msgstr "" + +#: ../channels/email/index.rst:21 +msgid "" +"Set up a :doc:`Microsoft 365 channel ` instead." +msgstr "" + +#: ../channels/email/index.rst:None ../channels/google/index.rst:None +#: ../channels/microsoft365/index.rst:None +msgid "Email settings panel" +msgstr "" + +#: ../channels/email/index.rst:37 +msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel" +msgstr "" + +#: ../channels/email/index.rst:29 +msgid "At this moment Zammad supports XOAUTH for the following providers:" +msgstr "" + +#: ../channels/email/index.rst:31 +msgid ":doc:`Google `" +msgstr "" + +#: ../channels/email/index.rst:32 +msgid "" +":doc:`Microsoft 365 (formerly Office 365) `" +msgstr "" + +#: ../channels/email/index.rst:34 +msgid "" +"Use above links to use the migration option instead of removing and re-" +"adding the channels. This will save precious time for something else!" +msgstr "" + +#: ../channels/email/index.rst:44 ../channels/email/index.rst:8 +msgid ":doc:`👥 Accounts `" +msgstr "" + +#: ../channels/email/index.rst:40 ../channels/email/index.rst:4 +msgid "" +"**Connect Zammad to your email provider** so that it can watch your inbox, " +"send auto-replies, and more." +msgstr "" + +#: ../channels/email/index.rst:43 ../channels/email/index.rst:7 +msgid "" +"(Self-hosted users may have already completed this step during new system " +"setup.)" +msgstr "" + +#: ../channels/email/index.rst:48 ../channels/email/index.rst:12 +msgid ":doc:`🗂️ Filters `" +msgstr "" + +#: ../channels/email/index.rst:47 ../channels/email/index.rst:11 +msgid "" +"**Make sure new tickets show up in the right place** with automated, if-this-" +"then-that rules for all incoming email." +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid ":doc:`📜 Signatures `" +msgstr "" + +#: ../channels/email/index.rst:51 ../channels/email/index.rst:15 +msgid "Customize signatures for all outgoing email." +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid ":doc:`⚙️ Settings `" +msgstr "" + +#: ../channels/email/index.rst:54 ../channels/email/index.rst:18 +msgid "Manage options like:" +msgstr "" + +#: ../channels/email/index.rst:56 ../channels/email/index.rst:20 +msgid "set the “From:” address on system notifications" +msgstr "" + +#: ../channels/email/index.rst:57 ../channels/email/index.rst:21 +msgid "raise the limit on attachment sizes" +msgstr "" + +#: ../channels/email/index.rst:58 ../channels/email/index.rst:22 +msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)" +msgstr "" + +#: ../channels/email/index.rst:60 ../channels/email/index.rst:24 +msgid "" +"Want to **manually edit email subjects** or **always copy parent messages " +"into your replies**?" +msgstr "" + +#: ../channels/email/index.rst:63 ../channels/email/index.rst:27 +msgid "Check the ✍️ :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:33 +msgid ":doc:`📇 Header manipulation `" +msgstr "" + +#: ../channels/email/index.rst:66 ../channels/email/index.rst:30 +msgid "Manipulate auto response behavior or incoming routing." +msgstr "" + +#: ../channels/email/index.rst:68 ../channels/email/index.rst:32 +msgid "🤓 This is a very advanced topic." +msgstr "" + +#: ../channels/email/index.rst:71 +msgid "Extra Options for Self-Hosted Users" +msgstr "" + +#: ../channels/email/index.rst:73 +msgid "If you’re too cool for POP3/IMAP/SMTP..." +msgstr "" + +#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:48 +#: ../system/integrations/checkmk/admin-panel-reference.rst:5 +msgid "Settings" +msgstr "" + +#: ../channels/email/settings.rst:8 +msgid "" +"Below you can find the currently available email-related settings. Most of " +"these settings have default values which can be found in this list as well." +msgstr "" + +#: ../channels/email/settings.rst:13 +msgid "" +"Some email-related settings are ticket-based settings, which is why they can " +"be found in the :doc:`/misc/composer`." +msgstr "" + +#: ../channels/email/settings.rst:17 +msgid "List of Settings" +msgstr "" + +#: ../channels/email/settings.rst:28 +msgid "" +"Notification Sender: Default value ``Notification Master ``" +msgstr "" + +#: ../channels/email/settings.rst:20 +msgid "" +"This is the default sender address for Zammad that affects all mails but " +"those generated because of replies (like triggers or agent-based mails). " +"Your customers normally will not see this address. This email address does " +"not need to receive and can't be assigned to a group." +msgstr "" + +#: ../channels/email/settings.rst:27 +msgid "" +"This address is relevant for agent notifications and password reset mails " +"(also affects customers)." +msgstr "" + +#: ../channels/email/settings.rst:39 +msgid "Additional follow-up detection" +msgstr "" + +#: ../channels/email/settings.rst:31 +msgid "" +"In some situations the normal follow-up detection is not enough. This might " +"be due to missing references in the subject (the ticket hook and number). " +"These options can help to recognize follow-ups to existing tickets." +msgstr "" + +#: ../channels/email/settings.rst:38 +msgid "" +"Please note that searching in attachment and body might lead to false follow-" +"up detection." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "Maximum Email Size: Default value ``10 MB``" +msgstr "" + +#: ../channels/email/settings.rst:42 +msgid "" +"This one is pretty obvious: It defines the maximum allowed size of an email " +"Zammad will fetch. Zammad will not fetch Mails that are bigger than this " +"option." +msgstr "" + +#: ../channels/email/settings.rst:48 +msgid "This technically also affects attachments for articles." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``" +msgstr "" + +#: ../channels/email/settings.rst:53 +msgid "" +"Upgraded installations will, by default, have the value set to ``no " +"(disabled``)." +msgstr "" + +#: ../channels/email/settings.rst:66 ../channels/email/settings.rst:95 +msgid "Option set to ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:57 +msgid "" +"This setting will cause Zammad to automatically reply to mails that exceed " +"the above mail size limit with a postmaster style mail. This will help your " +"user to understand that his mail did not arrive and won't be reviewed by you." +msgstr "" + +#: ../channels/email/settings.rst:64 +msgid "" +"Zammad will still download and remove (if enabled) the mail from the " +"mailbox. Instead of importing it to the database, it will save the affected " +"mail to ``/opt/zammad/tmp/oversized_mail/``." +msgstr "" + +#: ../channels/email/settings.rst:74 ../channels/email/settings.rst:104 +msgid "Option set to ``no``" +msgstr "" + +#: ../channels/email/settings.rst:69 +msgid "" +"If the option is set to no, Zammad will not reply to mails that are too big. " +"Your customer will **not notice** that the mail was too large! Instead, " +"Zammad will use the monitoring endpoint to alert its administrators that it " +"can't fetch a too large mail." +msgstr "" + +#: ../channels/email/settings.rst:74 +msgid "Learn more about :doc:`/system/monitoring`." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "Sender based on Reply-To header: Default value ``not set (-)``" +msgstr "" + +#: ../channels/email/settings.rst:77 +msgid "" +"This setting decides how Zammad should recognize its customers from emails " +"that contain a ``Reply-To`` header. This comes in useful if you're working " +"with contact forms that need to use reply to headers." +msgstr "" + +#: ../channels/email/settings.rst:83 +msgid "Option set to ``Take reply-to header as sender/from of email.``" +msgstr "" + +#: ../channels/email/settings.rst:82 +msgid "" +"This setting will overwrite the initial ``FROM`` to the value used in " +"``Reply-To`` completely." +msgstr "" + +#: ../channels/email/settings.rst:88 +msgid "" +"Option set to ``-`` or ``Take Reply-To header as sender/from of email and " +"use the real name of origin from.``" +msgstr "" + +#: ../channels/email/settings.rst:86 +msgid "" +"This setting will partially overwrite the initial ``FROM``. It uses the mail " +"address from the ``Reply-To`` header and uses the given name of the ``FROM`` " +"header, if given." +msgstr "" + +#: ../channels/email/settings.rst:104 +msgid "" +"Customer selection based on sender and receiver list: Default value ``yes``" +msgstr "" + +#: ../channels/email/settings.rst:91 +msgid "" +"This option decides how Zammad should react if an agent sends a email to it." +msgstr "" + +#: ../channels/email/settings.rst:94 +msgid "" +"The first user / email address from the recipient list will be used as the " +"ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:98 +msgid "The agent will be set as ticket customer." +msgstr "" + +#: ../channels/email/settings.rst:102 +msgid "" +"Currently agents can't be customers within the UI. While Email communication " +"works, agents can't see their own tickets (as a customer) if they don't have " +"access to the group." +msgstr "" + +#: ../channels/email/settings.rst:114 +msgid "Block Notifications" +msgstr "" + +#: ../channels/email/settings.rst:107 +msgid "" +"With the regex that can be defined here, you can ensure not to send any " +"notifications to specific systems. By default this especially affects " +"typical system addresses which can't receive emails anyway." +msgstr "" + +#: ../channels/email/settings.rst:111 +msgid "" +"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply." +"+?|no-reply|no-reply.+?)@.+?``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "" +"Sender Format: Default value ``Agent Name + FromSeparator + System Address " +"Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:117 +msgid "" +"This configures the display name used in the ``FROM`` header of mails Zammad " +"sends." +msgstr "" + +#: ../channels/email/settings.rst:122 +msgid "" +"This does not affect Notification mails (to agents) and password reset " +"mails. Emails that are not sent by agents (e.g. trigger-based notifications) " +"will always fallback to ``System Address Display Name`` if needed." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "" +"Option set to ``Agent Name + FromSeparator + System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:128 +msgid "" +"This will cause Zammad to set the ``FROM`` header to agent name and the " +"channel's display name, divided by a separator (configured below)." +msgstr "" + +#: ../channels/email/settings.rst:131 +msgid "Example: ``Christopher Miller via Chrispresso Inc.``." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Option set to ``System Address Display Name``" +msgstr "" + +#: ../channels/email/settings.rst:134 +msgid "" +"This will cause Zammad to always use the display name of the used channel in " +"the ``FROM`` header." +msgstr "" + +#: ../channels/email/settings.rst:137 +msgid "Example: ``Chrispresso Inc.``" +msgstr "" + +#: ../channels/email/settings.rst:146 +msgid "Option set to ``Agent Name``" +msgstr "" + +#: ../channels/email/settings.rst:140 +msgid "Zammad will use the agent's name which is very personal." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "" +"Usually you'd also want to remove the ticket slug from the subject in those " +"cases." +msgstr "" + +#: ../channels/email/settings.rst:0 +msgid "Learn more in :doc:`Settings → Ticket `." +msgstr "" + +#: ../channels/email/settings.rst:150 +msgid "Sender Format Separator: Default value ``via``" +msgstr "" + +#: ../channels/email/settings.rst:149 +msgid "" +"This is a can be a string you can freely choose. It divides the agent's name " +"and the display name of the channel whenever needed." +msgstr "" + +#: ../channels/email/settings.rst:158 +msgid "Ticket Subject Forward: Default value ``FWD``" +msgstr "" + +#: ../channels/email/settings.rst:153 +msgid "" +"The above string will be used on the subject if you forward an email from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:158 ../channels/email/settings.rst:166 +msgid "``:`` will be automatically appended to the above string." +msgstr "" + +#: ../channels/email/settings.rst:166 +msgid "Ticket Subject Reply: Default value ``RE``" +msgstr "" + +#: ../channels/email/settings.rst:161 +msgid "" +"The above string will be used on the subject if you reply to a mail from " +"Zammad." +msgstr "" + +#: ../channels/email/settings.rst:180 +msgid "Ticket Subject Size: Default value ``110``" +msgstr "" + +#: ../channels/email/settings.rst:169 +msgid "" +"This setting enforces a maximum length for subjects when replying. If the " +"subject you're using for your reply is too long, Zammad will automatically " +"truncate the length and insert ``[...]`` to show it has shortened the " +"subject." +msgstr "" + +#: ../channels/email/settings.rst:174 +msgid "Example: ``RE: Test somew[...] [Ticket#123456]``" +msgstr "" + +#: ../channels/email/settings.rst:178 +msgid "" +"This does **not** limit ticket titles within the UI, just the subjects when " +"replying to an email." +msgstr "" + +#: ../channels/email/settings.rst:183 +msgid "Enhanced settings" +msgstr "" + +#: ../channels/email/settings.rst:185 +msgid "" +"Some less relevant settings can be changed via rails console if needed. As " +"an example, Zammad allows you to send all outgoing communication to a BCC " +"address for archiving reasons if needed. You can find the needed commands " +"`within the advanced customization settings`_." +msgstr "" + +#: ../channels/email/signatures.rst:2 +msgid "Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:8 +msgid "" +"You can create a separate signature for each group in Zammad. The individual " +"signatures can be created and edited here." +msgstr "" + +#: ../channels/email/signatures.rst:11 +msgid "" +"Afterwards, the existing (and active) signatures are available in the group " +"editing mask:" +msgstr "" + +#: ../channels/email/signatures.rst:16 +msgid "" +"Each group can be assigned its own signature, but they can also all use the " +"same signature." +msgstr "" + +#: ../channels/email/signatures.rst:21 +msgid "Dynamic Signatures" +msgstr "" + +#: ../channels/email/signatures.rst:23 +msgid "" +"To individualize the signatures, it is possible to automatically load " +"specific information into a signature via :doc:`/system/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 " +"*Text* box of the signature editor." +msgstr "" + +#: ../channels/email/signatures.rst:32 +msgid "" +"Please keep in mind that specific information might not be available during " +"ticket creation. The best example here is the ticket number / id. Specific " +"information are created with submitting the ticket and thus are not " +"available before submitting." +msgstr "" + +#: ../channels/email/signatures.rst:40 +msgid "" +"Here is an example of a signature with variables and the result when you " +"write a mail:" +msgstr "" + +#: ../channels/facebook.rst:2 ../settings/security/third-party/facebook.rst:2 +msgid "Facebook" +msgstr "" + +#: ../channels/facebook.rst:6 +msgid "" +"Please note that this part of our documentation currently is outdated. We " +"currently are working on solutions for this topic." +msgstr "" + +#: ../channels/facebook.rst:9 +msgid "" +"You can connect Facebook Accounts with Zammad. You need to connect your " +"Zammad with Facebook first:" +msgstr "" + +#: ../channels/facebook.rst:12 +msgid "For this start at: https://developers.facebook.com/apps/" +msgstr "" + +#: ../channels/facebook.rst:18 +msgid "Click on “Create App ID\" and enter app name" +msgstr "" + +#: ../channels/facebook.rst:39 +msgid "***Configure Zammad as Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:41 +msgid "Go to “Admin -> Channels -> Facebook”" +msgstr "" + +#: ../channels/facebook.rst:42 +msgid "" +"Click on “Connect Facebook App” and enter your “App ID”, “App Secret” and " +"verify the “Callback URL”." +msgstr "" + +#: ../channels/facebook.rst:45 +msgid "Done, your Zammad is configured as Facebook App now." +msgstr "" + +#: ../channels/facebook.rst:48 +msgid "***Link your Facebook Page to your Zammad Facebook app***" +msgstr "" + +#: ../channels/facebook.rst:50 +msgid "" +"Now you need to link your Facebook Page from which you want to get posts and " +"send out comments." +msgstr "" + +#: ../channels/facebook.rst:53 +msgid "" +"Click on “Add Account”, then you will see the authorize app page of " +"Facebook. Click on “authorize app”." +msgstr "" + +#: ../channels/facebook.rst:60 +msgid "" +"You will get redirected back to Zammad. Now you need to configure your " +"search keys, where mentions should get routed." +msgstr "" + +#: ../channels/facebook.rst:65 +msgid "" +"After you are done, you will get an overview of all linked Facebook Accounts." +msgstr "" + +#: ../channels/facebook.rst:70 +msgid "***Start using your new channel***" +msgstr "" + +#: ../channels/facebook.rst:72 +msgid "" +"Start and write a post to your page, short time later you will have a new " +"ticket in Zammad." +msgstr "" + +#: ../channels/facebook.rst:75 +msgid "" +"Just click on the reply button (as you do it for emails) to send a comment." +msgstr "" + +#: ../channels/form.rst:2 +msgid "Forms" +msgstr "" + +#: ../channels/form.rst:4 +msgid "" +"Feedback or contact forms are used on websites quite often. Usually they " +"will generate an email which will be sent to somebody who forwards it and so " +"on. With Zammad it’s quite easy to integrate these forms into your website " +"and directly generate tickets with them. In just 2 minutes." +msgstr "" + +#: ../channels/form.rst:None +msgid "Zammad form management page" +msgstr "" + +#: ../channels/form.rst:13 ../manage/trigger/limitations.rst:2 +#: ../misc/object-conditions/basics.rst:12 +#: ../misc/object-conditions/index.rst:7 +#: ../settings/security/third-party/microsoft.rst:21 +#: ../system/core-workflows/limitations.rst:2 +#: ../system/integrations/cti/includes/introduction.include.rst:18 +#: ../system/integrations/elasticsearch.rst:25 +#: ../system/integrations/ldap/index.rst:31 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Limitations" +msgstr "" + +#: ../channels/form.rst:15 +msgid "Please note the following limitations:" +msgstr "" + +#: ../channels/form.rst:17 +msgid "The fields provided by the form are limited to the following:" +msgstr "" + +#: ../channels/form.rst:19 ../manage/groups/settings.rst:14 +#: ../manage/scheduler.rst:37 ../manage/slas/how-do-they-work.rst:28 +#: ../manage/templates.rst:33 +msgid "Name" +msgstr "" + +#: ../channels/form.rst:21 ../system/maintenance.rst:93 +#: ../system/maintenance.rst:34 +msgid "Message" +msgstr "" + +#: ../channels/form.rst:22 +msgid "Attachment upload (optional)" +msgstr "" + +#: ../channels/form.rst:23 +msgid "Checkbox for custom agreement text (optional)" +msgstr "" + +#: ../channels/form.rst:25 +msgid "As of now only one dedicated form per instance is possible" +msgstr "" + +#: ../channels/form.rst:30 +msgid "Zammad comes with certain settings for forms." +msgstr "" + +#: ../channels/form.rst:39 ../manage/groups/settings.rst:102 +#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 +#: ../manage/scheduler.rst:72 ../manage/templates.rst:43 +#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:45 +msgid "Active" +msgstr "" + +#: ../channels/form.rst:33 +msgid "" +"By default the form channel is *inactive*. Use the switch in front of \"Form" +"\" to activate this channel." +msgstr "" + +#: ../channels/form.rst:38 +msgid "" +"Forms will not be displayed on your website if the channel is not active. " +"This does not affect the form preview on the channels setting page." +msgstr "" + +#: ../channels/form.rst:43 +msgid "Group selection for ticket creation" +msgstr "" + +#: ../channels/form.rst:42 +msgid "" +"The group you set here defines where tickets should be created if they're " +"supplied by Zammad's web form." +msgstr "" + +#: ../channels/form.rst:46 +msgid "Designer" +msgstr "" + +#: ../channels/form.rst:48 +msgid "" +"This section helps you to configure your form in the channel's scope. If " +"you're happy with what you've chosen, you're provided with the code you need " +"to copy to your website." +msgstr "" + +#: ../channels/form.rst:54 +msgid "" +"The designer's changes *are not* stored anywhere in Zammad. This means that " +"the provided source code needs to be copied every time you change settings " +"here." +msgstr "" + +#: ../channels/form.rst:None +msgid "" +"Zammad's form designer supports you with the initial configuration\n" +"of your form." +msgstr "" + +#: ../channels/form.rst:63 +msgid "So let's talk about the options the designer provides." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Title of the form" +msgstr "" + +#: ../channels/form.rst:66 +msgid "" +"Choose how the heading of the form should be called. This setting is only " +"relevant if you choose to display the form title in the form." +msgstr "" + +#: ../channels/form.rst:70 +msgid "Default: ``Feedback Form``" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Name of form submit button" +msgstr "" + +#: ../channels/form.rst:73 +msgid "" +"If Zammad's default display name of the submit button does not fit, you can " +"provide your own wording with this option. It will be used every time the " +"form is shown." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Message after sending form" +msgstr "" + +#: ../channels/form.rst:78 +msgid "" +"After your user pressed the submit button, they will be provided with a " +"message containing the ticket number of the newly created ticket." +msgstr "" + +#: ../channels/form.rst:81 +msgid "Default *after* sending a form will look like so:" +msgstr "" + +#: ../channels/form.rst:0 +msgid "Options" +msgstr "" + +#: ../channels/form.rst:89 +msgid "" +"Zammad provides the following additional configuration options for your form." +msgstr "" + +#: ../channels/form.rst:95 +msgid "Enable debugging for implementation" +msgstr "" + +#: ../channels/form.rst:92 +msgid "" +"This option activates detailed debug information in your browser's developer " +"tools console." +msgstr "" + +#: ../channels/form.rst:95 +msgid "This option *should not* be active on productive forms!" +msgstr "" + +#: ../channels/form.rst:99 +msgid "Show title in form" +msgstr "" + +#: ../channels/form.rst:98 +msgid "" +"This setting belongs to the setting ``Title of the form`` and will provide " +"the form title within the form dialogue if selected." +msgstr "" + +#: ../channels/form.rst:111 +msgid "Start modal dialog for form" +msgstr "" + +#: ../channels/form.rst:102 +msgid "" +"If selected, the form will be opened in a modal by clicking a button. Not " +"selecting this option allows you to natively integrate the form within your " +"website's body." +msgstr "" + +#: ../channels/form.rst:106 +msgid "This option is set by default." +msgstr "" + +#: ../channels/form.rst:110 +msgid "" +"No matter what you select here, the form *is always* loaded completely if " +"your user browses the page containing the form." +msgstr "" + +#: ../channels/form.rst:118 +msgid "" +"Don't load CSS for the form You need to generate your own CSS for the form." +msgstr "" + +#: ../channels/form.rst:114 +msgid "" +"By default Zammad's form comes with basic CSS. This may not fit your " +"website's design or even interfere with it." +msgstr "" + +#: ../channels/form.rst:117 +msgid "" +"Selecting this option allows you to freely design the form without having to " +"overwrite existing directives." +msgstr "" + +#: ../channels/form.rst:131 +msgid "Add attachment option to upload" +msgstr "" + +#: ../channels/form.rst:121 +msgid "Allows your user to upload **one attachment** to the form." +msgstr "" + +#: ../channels/form.rst:123 +msgid "**🤓 Watch allowed attachment sizes here**" +msgstr "" + +#: ../channels/form.rst:125 +msgid "" +"This function *is not* limited technically. The only limitation that applies " +"is your web servers upload limit." +msgstr "" + +#: ../channels/form.rst:128 +msgid "**SaaS only**" +msgstr "" + +#: ../channels/form.rst:130 +msgid "" +"If you're with Zammad hosted, attachments are limited by the package you've " +"chosen." +msgstr "" + +#: ../channels/form.rst:146 +msgid "Add agreement text before submit" +msgstr "" + +#: ../channels/form.rst:134 +msgid "" +"If enabled, this will allow you define a text that the form will display " +"together with a checkbox. Thereby you can ensure your form conforms to legal " +"requirements, e.g. by providing data privacy notes that the user has to " +"accept before submitting the form." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Screencast showing a sample on how to configure the agreement\n" +"text setting" +msgstr "" + +#: ../channels/form.rst:143 +msgid "" +"Zammad provides a free text form with limited capabilities. Use the *🔗 " +"Weblink* button to add links to marked text passages." +msgstr "" + +#: ../channels/form.rst:146 +msgid "This allows you to link e.g. to your data privacy or ToS information." +msgstr "" + +#: ../channels/form.rst:149 ../manage/scheduler.rst:57 +#: ../manage/slas/how-do-they-work.rst:37 +msgid "Preview" +msgstr "" + +#: ../channels/form.rst:151 +msgid "" +"Below the form options, Zammad provides a preview section to visualize the " +"settings you've just chosen. By default you'll see a button named *Feedback*." +msgstr "" + +#: ../channels/form.rst:154 +msgid "Clicking on the button will open the form modal." +msgstr "" + +#: ../channels/form.rst:158 +msgid "" +"If the form channel is set to active, you already are able to create tickets " +"even from this preview mode." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the preview section for the just configured form" +msgstr "" + +#: ../channels/form.rst:166 ../system/integrations/cti/generic.rst:7 +#: ../system/integrations/cti/placetel.rst:12 +#: ../system/integrations/cti/sipgate.rst:12 +#: ../system/integrations/zabbix.rst:10 +msgid "Requirements" +msgstr "" + +#: ../channels/form.rst:168 +msgid "" +"The requirement section provides you with everything you need in order to " +"apply Zammad's web form to your website. It basically consists of two parts." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Header section" +msgstr "" + +#: ../channels/form.rst:172 +msgid "" +"The first code block provides you with Zammad's current jQuery dependency. " +"This script section usually belongs to your website's header section." +msgstr "" + +#: ../channels/form.rst:177 +msgid "" +"The channel form suggests the following script tag which loads the " +"javascript libary required **from an external site**. This may not suite " +"your local requirements. You can use locally hosted jQuery version, " +"**however** the version is fixed." +msgstr "" + +#: ../channels/form.rst:186 +msgid "Do not mix jQuery versions - it's likely to break something." +msgstr "" + +#: ../channels/form.rst:0 +msgid "Body section" +msgstr "" + +#: ../channels/form.rst:189 +msgid "The second code block is the actual code required for your form to run." +msgstr "" + +#: ../channels/form.rst:191 +msgid "" +"The first line containing ``id=\"zammad-feedback-form\"`` highly depends on " +"the settings selected above. This part belongs into the place you actually " +"want the form or form button to appear." +msgstr "" + +#: ../channels/form.rst:195 +msgid "" +"The rest can either be placed at the same level or somewhere else on the " +"same page." +msgstr "" + +#: ../channels/form.rst:200 +msgid "" +"This code block is updated automatically when changing settings in the " +"designer above." +msgstr "" + +#: ../channels/form.rst:205 +msgid "" +"These statements *highly* depend on your website. As you're responsible for " +"your own website, you're on your own figuring out where exactly to place " +"what." +msgstr "" + +#: ../channels/form.rst:209 +msgid "" +"Take the Zammad website as an example, the embedded form version can look " +"like the following if you apply custom CSS to it." +msgstr "" + +#: ../channels/form.rst:None +msgid "Screenshot showing the zammad.com website with embedded web form" +msgstr "" + +#: ../channels/form.rst:218 +msgid "Potential Spam Issue" +msgstr "" + +#: ../channels/form.rst:220 +msgid "" +"The Form function could be abused by sending a high amount of messages / " +"tickets to your Zammad instance. If you do not use Zammad Forms: **disable** " +"them." +msgstr "" + +#: ../channels/form.rst:224 +msgid "" +"But don't worry! Zammad does limit the maximum count of created tickets " +"based on different criteria. It also ensures that the email address being " +"used is valid (with MX-Check on the email's domain)." +msgstr "" + +#: ../channels/form.rst:228 +msgid "Form settings to limit ticket creation" +msgstr "" + +#: ../channels/form.rst:232 +msgid "Option" +msgstr "" + +#: ../channels/form.rst:233 +msgid "Default value" +msgstr "" + +#: ../channels/form.rst:234 ../manage/public-links.rst:61 +#: ../system/subscription/billing.rst:57 +msgid "Description" +msgstr "" + +#: ../channels/form.rst:235 +msgid "``form_ticket_create_by_ip_per_hour``" +msgstr "" + +#: ../channels/form.rst:236 +msgid "``20``" +msgstr "" + +#: ../channels/form.rst:237 +msgid "Limits ticket creation per IP and hour to 20 tickets" +msgstr "" + +#: ../channels/form.rst:238 +msgid "``form_ticket_create_by_ip_per_day``" +msgstr "" + +#: ../channels/form.rst:239 +msgid "``240``" +msgstr "" + +#: ../channels/form.rst:240 +msgid "Limits ticket creation per IP and day to 240 tickets" +msgstr "" + +#: ../channels/form.rst:241 +msgid "``form_ticket_create_per_day``" +msgstr "" + +#: ../channels/form.rst:242 +msgid "``5000``" +msgstr "" + +#: ../channels/form.rst:243 +msgid "Limits ticket creation for forms to 5000 tickets per day" +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"You can change these default values. Please keep in mind, that setting those " +"values higher might lead to problems in term of created tickets." +msgstr "" + +#: ../channels/form.rst:0 +msgid "" +"Please note that the following changes require console access to your Zammad " +"host." +msgstr "" + +#: ../channels/form.rst:253 +msgid "**Change the ticket creation per IP and hour to 10**::" +msgstr "" + +#: ../channels/form.rst:257 +msgid "**Change the ticket creation per IP and hour to 50**::" +msgstr "" + +#: ../channels/form.rst:261 +msgid "**Change the ticket creation per day to 500**::" +msgstr "" + +#: ../channels/form.rst:267 +msgid "Further options to make it harder" +msgstr "" + +#: ../channels/form.rst:269 +msgid "" +"Another way to make it harder for bots to automate against your Zammad " +"instance is to change the location of ``form.js`` ( ``/opt/zammad/assets/" +"form/form.js`` )." +msgstr "" + +#: ../channels/form.rst:273 +msgid "" +"Please keep in mind if you change the location of ``form.js`` (by e.g. " +"copying) that you need to ensure that your ``form.js`` stays up to date if " +"you update Zammad." +msgstr "" + +#: ../channels/form.rst:277 +msgid "" +"It's not recommended to delete form.js from it's location in that case, but " +"to forbid access to it via your web server configuration." +msgstr "" + +#: ../channels/google/accounts.rst:22 ../channels/microsoft365/accounts.rst:22 +msgid ":doc:`accounts/register-app`" +msgstr "" + +#: ../channels/google/accounts.rst:14 +msgid "" +"Use the **Connect Google App** dialog to register Zammad as an OAuth app on " +"Google." +msgstr "" + +#: ../channels/google/accounts.rst:17 ../channels/microsoft365/accounts.rst:17 +msgid "(This step is **required**; read on to learn why.)" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Registering Zammad as a Google OAuth app" +msgstr "" + +#: ../channels/google/accounts.rst:25 ../channels/microsoft365/accounts.rst:25 +msgid "Use the **Add Account** dialog to connect your account." +msgstr "" + +#: ../channels/google/accounts.rst:27 ../channels/microsoft365/accounts.rst:27 +msgid "You're migrating existing email channels? Look below!" +msgstr "" + +#: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 +msgid "Adding your gmail account to Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:41 ../channels/microsoft365/accounts.rst:41 +msgid ":doc:`accounts/migrate-from-email-channel`" +msgstr "" + +#: ../channels/google/accounts.rst:35 ../channels/microsoft365/accounts.rst:35 +msgid "" +"Use the *Migrate now!* button within your email channels to quickly move " +"your mailboxes to Microsoft 365. You can roll back if things hit the fan!" +msgstr "" + +#: ../channels/google/accounts.rst:0 +#: ../channels/google/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Google" +msgstr "" + +#: ../channels/google/accounts.rst:0 +msgid "Adding new aliases to your gmail account in Zammad" +msgstr "" + +#: ../channels/google/accounts.rst:60 +msgid "🤔 **How do I use my Gmail account for outgoing system notifications?**" +msgstr "" + +#: ../channels/google/accounts.rst:62 ../channels/microsoft365/accounts.rst:64 +msgid "" +"On **subscription/cloud-hosted instances**, you can’t. Notifications will " +"always come from “Notification Master ”." +msgstr "" + +#: ../channels/google/accounts.rst:66 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Gmail " +"account for automated, outgoing messages is risky: users who exceed Google’s " +"`email sending limits `_ can " +"have their accounts suspended." +msgstr "" + +#: ../channels/google/accounts.rst:72 +msgid "" +"Set up a generic :doc:`email channel ` instead, the " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Google Developer settings, you can begin connecting Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:14 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:20 +#: ../channels/microsoft365/accounts/account-setup.rst:19 +msgid "" +"Make sure to :doc:`disable this behavior ` prior adding an " +"email account, and to turn it back on once all your messages have been " +"imported." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:25 +#: ../channels/microsoft365/accounts/account-setup.rst:30 +msgid "🚛 Migrate an Existing Email Channel" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:27 +msgid "" +"If you’ve already added your Google account as a regular email channel, " +"you’ll have to convert it to a Google channel eventually: Google is planning " +"to end support for simple password authentication in third-party email " +"clients (like Zammad)." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:32 +#: ../channels/microsoft365/accounts/account-setup.rst:37 +msgid "Please refer the :doc:`migrate-from-email-channel` guide." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:35 +#: ../channels/microsoft365/accounts/account-setup.rst:88 +msgid "Add a New Account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Google account to Zammad" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:42 +msgid "" +"Click **Add Account** to connect your Gmail / G Suite accounts to Zammad. " +"You will be redirected to a Google sign-in and confirmation page." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:45 +msgid "" +"Any aliases registered in your Gmail settings will be imported automatically." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:0 +msgid "Google warning for unverified OAuth apps" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:54 +msgid "" +"Google has a stringent verification process to protect users from third-" +"party websites that use OAuth to access their data. Since you *are* the " +"third-party website here, you can safely ignore this warning." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:70 +#: ../channels/microsoft365/accounts/account-setup.rst:132 +msgid "" +"Specify which folder (or *label*) to fetch from, or leave empty to fetch " +"from ``INBOX``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:73 +#: ../channels/microsoft365/accounts/account-setup.rst:135 +msgid "" +"If specifying a nested folder, be sure to use the full path; *e.g.,* " +"``Inquiries/Tech-Support``." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:113 +#: ../channels/microsoft365/accounts/account-setup.rst:175 +msgid "After adding the account" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:101 +#: ../channels/microsoft365/accounts/account-setup.rst:163 +msgid "" +"After successfully adding the Microsoft 365 mail account, you can adjust the " +"default group Zammad is going to assign incoming new tickets to." +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +#: ../channels/microsoft365/accounts/account-setup.rst:183 +msgid "I successfully added my account, but Zammad isn’t fetching new email" +msgstr "" + +#: ../channels/google/accounts/account-setup.rst:119 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, " +"are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Google channels is (almost) **just like it is in email " +"channels**, so this article is lifted (almost) verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:10 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:11 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:10 +msgid "Fetch Preferences" +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:2 +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:2 +msgid "" +"Click **Edit** on inbound account details to change how messages are " +"retrieved from your account." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed description " +"of each option." +msgstr "" + +#: ../channels/google/accounts/managing-accounts.delete-note.rst:8 +msgid "" +"(There’s no need to manage orphaned email addresses like you would on an " +"email channel. In Google channels, aliases are connected to your Gmail " +"account, which means they can be imported and purged automatically.)" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Google channel" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing Google " +"accounts from the Email channel to the Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:7 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7 +msgid "🧐 **Zammad is expecting specific settings**" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``imap.gmail.com`` for IMAP and ``smtp.gmail.com`` for SMTP." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:12 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Google accounts before migrating. However, if you don't, Zammad will ask you " +"to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:16 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to Google " +"and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:20 +msgid "" +"After you pressed next you'll be redirect to Zammad's Google channel " +"overview. Your channel, if successful, is now migrated to an Google channel." +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:29 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31 +msgid "Rolling back the migration" +msgstr "" + +#: ../channels/google/accounts/migrate-from-email-channel.rst:31 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:33 +msgid "" +"In case something went wrong, Zammad allows you to roll back the migration " +"for up to 7 days. For this time period Zammad will remember your original " +"credentials and restore it if needed. These information will be removed " +"entirely after 7 days." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:2 +#: ../channels/microsoft365/accounts/register-app.rst:2 +msgid "Register an OAuth App" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:4 +msgid "" +"Setting up a new Gmail / G Suite account? Because of Google’s strict " +"security policies, it’s not as simple as entering your username and password." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Google account as an **OAuth " +"app** via the Google Developer settings panel. Once that’s done, you’ll be " +"able to connect as many Gmail accounts to Zammad as you want, using only " +"active Gmail browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:14 +#: ../channels/microsoft365/accounts/register-app.rst:14 +msgid "🤔 **What the heck is OAuth?**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Google/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screenshot of website with various OAuth sign-in options" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Google). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Gmail account is a two-stage process: first, you have to register Zammad as " +"a website that wishes to access Google user data; then, you have to add " +"yourself as a Google user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:38 +#: ../channels/microsoft365/accounts/register-app.rst:40 +msgid "Step-by-Step" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:40 +msgid "" +"To get started, head over to `Google’s Developer settings panel `_." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:43 +msgid "**Create a new project**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:45 +msgid "" +"For the purposes of this guide, a “project” and an OAuth app are the same " +"thing. You may name it whatever you wish." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of new project creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:52 +msgid "**Enable & add the Gmail API**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:54 +msgid "Use the **➕ Enable APIs and Services** button to start your search." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of enabling Gmail API in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:60 +msgid "**Set up the OAuth consent screen**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:62 +msgid "" +"Configure who can use your app, what kind of access it’s asking for, and a " +"few fine print details (like a link to Zammad’s privacy policy)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:65 +msgid "" +"This information will be displayed in the process of connecting a Gmail " +"account to Zammad, when users are redirected to Google for sign-in/" +"confirmation." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of OAuth consent screen setup in Google Developer\n" +"settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:79 +msgid "User Type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:75 +msgid "This option is only available to G Suite users." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:77 +msgid "" +"If you have the option, choose **Internal** (unless you plan on creating " +"channels for Gmail addresses from outside your G Suite domain)." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Scopes for Google APIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:82 +msgid "Add **Gmail API: https://mail.google.com**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:84 +msgid "**Generate OAuth credentials**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:86 +msgid "Click on **➕ Create credentials > OAuth client ID** to begin." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "Screencast demo of OAuth app creation in Google Developer settings" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Application type" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:93 +msgid "Choose **Web application**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:100 +msgid "Authorized redirect URIs" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:96 +msgid "" +"*E.g.,* ``https://your-domain.com/api/v1/external_credentials/google/" +"callback``" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:99 +msgid "" +"Find it in the Zammad admin panel under **Channels > Google > Connect Google " +"App > Your callback URL**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:102 +msgid "**Connect your Google app in Zammad**" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:104 +msgid "" +"Copy your new OAuth app’s credentials (**client ID** and **client secret**) " +"into Zammad in the admin panel, under **Channels > Google > Connect Google " +"App**." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Gmail OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:113 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Gmail accounts to Zammad." +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "My OAuth credentials stopped working all of a sudden" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:119 +msgid "Did you recently reset your Google password?" +msgstr "" + +#: ../channels/google/accounts/register-app.rst:121 +msgid "" +"(Google invalidates all your OAuth tokens whenever you change your password. " +"Generate a new one per Steps 4 and 5 above.)" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Google channels work (almost) **just like they do in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:1 +msgid "" +"👀 **Secondary addresses must be added and verified in your Gmail settings " +"first.**" +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:3 +msgid "" +"Gmail has its own process for adding and verifying aliases (under **Settings " +"> Accounts and Import > Send mail as**). If you add an alias here before " +"adding it in your Gmail settings, Google will refuse to dispatch it." +msgstr "" + +#: ../channels/google/accounts/secondary-addresses.warning.rst:8 +msgid "" +"G Suite users may need to contact their administrators in order to add " +"aliases in their Gmail settings." +msgstr "" + +#: ../channels/google/email-headers.rst:3 +msgid "" +"EMail header manipulation in Google channels work **just like in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters.rst:3 +msgid "" +"Filters in Google channels are **just like filters in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/filters/system-filters.rst:3 +msgid "" +"System Filters in Google channels are **just like system filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/index.rst:2 ../settings/security/third-party/google.rst:2 +msgid "Google" +msgstr "" + +#: ../channels/google/index.rst:13 +msgid "Connect a Gmail or G Suite account to Zammad." +msgstr "" + +#: ../channels/google/index.rst:19 +msgid "" +"Google channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/google/index.rst:22 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Google’s strict security measures." +msgstr "" + +#: ../channels/google/settings.rst:3 +msgid "" +"Settings in Google channels are **just like settings in email channels**, so " +"this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/google/signatures.rst:3 +msgid "" +"Signatures in Google channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:14 +msgid "" +"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth " +"app on Microsoft." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Registering Zammad as a Microsoft OAuth app" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0 +msgid "Migrate an existing email channel to Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:0 +msgid "Adding new aliases to your Microsoft account in Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:60 +msgid "🤔" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:62 +msgid "" +"**How do I use my Microsoft 365 account for outgoing system notifications?**" +msgstr "" + +#: ../channels/microsoft365/accounts.rst:68 +msgid "" +"On **self-hosted instances**, we still don’t recommend it. Using a Microsoft " +"account for automated, outgoing messages is risky: users who exceed " +"Microsoft’s `email sending limits`_ can have their accounts suspended." +msgstr "" + +#: ../channels/microsoft365/accounts.rst:73 +msgid "" +"Set up a generic :doc:`email channel ` instead, then " +"use the :ref:`Email Notification ` setting." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:4 +msgid "" +"After you’ve :doc:`registered Zammad as an OAuth app ` in your " +"Azure Portal, you can begin connecting Microsoft accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:13 +msgid "" +"Use the *Keep Messages on Server* setting to :ref:`disable this behavior " +"`." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:23 +msgid "🤓 **Shared mailboxes are possible...**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:25 +msgid "" +"For this to function ensure to set a password for the account in question. " +"You'll need these credentials to authenticate against later during adding " +"the account." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:32 +msgid "" +"If you’ve already added your Microsoft 365 account as a regular email " +"channel, you’ll have to convert it to a Microsoft 365 channel eventually: " +"Microsoft is planning to end support for simple password authentication in " +"third-party email clients (like Zammad)." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:40 +msgid "Requesting administrator consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:44 +msgid "" +"This step is only required if you didn't consent the permissions in App " +"registration as administrator on behalf of your users. If you do not use " +"this kind of security measurement, simply skip to `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:66 +msgid "Requesting the consent" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:50 +msgid "" +"Within Zammad click on **Request Admin Consent** in order to request consent " +"from your administrators. This is required in some tenants." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:55 +msgid "" +"If your admin already provided consent, you'll be automatically " +"authenticated, if this happens, continue with `Add a New Account`_." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:58 +msgid "" +"After authenticating against Microsoft and providing a reason for your " +"request, you'll be redirect to the Zammad app. Zammad will then tell you to " +"wait for your administrators consent. The consent grant or denial will be " +"sent by mail." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Click on Request Admin Consent if your administrator did not yet grant\n" +"the Zammad app for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:85 +msgid "Granting the consent (admin users)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:69 +msgid "" +"Within **Enterprise applications** go to **Admin consent requests**. You'll " +"find all your user grant requests here." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:72 +msgid "" +"Clicking on a request allows you to review which user requested the consent " +"for what app. Click on **Review permissions and consent** to start the grant " +"process. You'll be asked for credentials - these credentials are the " +"administrator credentials *not* the ones of the mailbox user to add." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:77 +msgid "" +"After you've granted the request, continue with `Add a New Account`_. (As " +"mentioned in :ref:`Step 3.1 of the App registration " +"`)" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "" +"Within Enterprise applications grant requests within admin consent\n" +"requests" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:94 +msgid "" +"Below shown screencast shows the authentication process with enabled admin " +"consent and already tenant wide granted permission." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:97 +msgid "" +"If you're not using admin consent in your organization or you're " +"authenticating a personal microsoft account, you'll see an additional " +"permission dialogue you'll have to approve." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:0 +msgid "Authentication dialogue for non admin consented users" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:113 +msgid "" +"Click **Add Account** to connect your Microsoft 365 / Outlook accounts to " +"Zammad. You will be redirected to a Microsoft sign-in and confirmation page." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:117 +msgid "🕵️ **Aliases are not imported automatically.**" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:119 +msgid "See :doc:`secondary-addresses` to add them yourself." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:None +msgid "Click on Add Account to add your Microsoft 365 account to Zammad" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:181 +msgid "" +"If you specified a :ref:`custom folder/label to fetch from `, are you sure incoming mail is arriving in that folder?" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:193 +msgid "" +"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``" +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:186 +msgid "" +"This is a Microsoft 365 specific issue which you have to solve with " +"Microsoft. However, you can have a look at `Microsofts documentation`_ which " +"might allow you to solve the issue on your own." +msgstr "" + +#: ../channels/microsoft365/accounts/account-setup.rst:190 +msgid "" +"As soon as the issue has been fixed, the Zammad channel will recover " +"automatically." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.rst:1 +msgid "" +"Managing accounts in Microsoft 365 channels is (almost) **just like it is in " +"email channels**, so this article is lifted (almost) verbatim from :doc:" +"`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5 +msgid "" +"See :ref:`New Account Settings ` for a detailed " +"description of each option." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:2 +msgid "Migrate from Email channel to Microsoft 365 channel" +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:4 +msgid "" +"Zammad provides a migration logic that allows you to migrate existing " +"Microsoft 365 accounts from the Email channel to the Microsoft 365 channel." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:9 +msgid "" +"In order for Zammad to display the migration option, it expects the channels " +"hostname to be ``outlook.office365.com`` for IMAP and ``smtp.office365.com`` " +"for SMTP." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:13 +msgid "" +"The easiest way to start the migration is to :doc:`register-app` for your " +"Microsoft accounts before migrating. However, if you don't, Zammad will ask " +"you to provide your app credentials before allowing you to continue." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:17 +msgid "" +"If you're ready to go, simply click on the *Migrate now!* button in the red " +"banner of the email channel in question. Zammad will redirect you to " +"Microsoft and request you to authenticate and consent to said account." +msgstr "" + +#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:21 +msgid "" +"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel " +"overview. Your channel, if successful, is now migrated to an Microsoft 365 " +"channel." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:4 +msgid "" +"Setting up a new Microsoft365 / Outlook account? Because of Microsoft's " +"strict security policies, it’s not as simple as entering your username and " +"password." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:8 +msgid "" +"First, you’ll have to connect Zammad to your Microsoft account as an **OAuth " +"app** via the Microsoft Azure Portal. Once that’s done, you’ll be able to " +"connect as many Microsoft 365 accounts to Zammad as you want, using only " +"active Microsoft 365 browser sessions (no usernames or passwords required)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:16 +msgid "" +"If you’ve ever used a website that lets you “Sign in with Google/Facebook/" +"Twitter”, you’ve used OAuth. OAuth is a way for you to let a third-party " +"website see a tiny slice of your Microsoft/Facebook/Twitter account data " +"without giving them your password (which would let them see *everything*)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:26 +msgid "" +"When a third-party website wants to use OAuth, it has to **register with the " +"provider first** (*i.e.,* Microsoft). This way, the provider knows who’s " +"receiving its users’ data, and can give users a way to revoke access if they " +"change their minds." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:31 +msgid "" +"In this case, **Zammad is that third-party website**. That’s why adding a " +"Microsoft account is a two-stage process: first, you have to register Zammad " +"as a website that wishes to access Microsoft user data; then, you have to " +"add yourself as a Microsoft user who agrees to let Zammad fetch your email." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:42 +msgid "To get started, head over to `Microsoft’s Azure Portal`_." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:47 +msgid "🔑 **Use an admin account for your organization.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:49 +msgid "" +"Otherwise, an admin will have to approve your changes before they can take " +"effect." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:52 +msgid "**Add an App Registration**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:54 +msgid "Under **App Registrations > ➕ New Registration**, use the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "Supported account types" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:58 +msgid "" +"Choose the option that’s right for your organization (or click *Help me " +"choose...* if you’re not sure)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:61 +#: ../settings/security/third-party/microsoft.rst:26 +msgid "" +"Accounts in this organizational directory only (Default Directory only - " +"Single tenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:63 +#: ../settings/security/third-party/microsoft.rst:28 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:65 +#: ../settings/security/third-party/microsoft.rst:30 +msgid "" +"Accounts in any organizational directory (Any Azure AD directory - " +"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:71 +msgid "🙅 **The “Personal Microsoft accounts only” option is not supported.**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:79 +msgid "Redirect URI" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:74 +msgid "" +"**Web** > *E.g.,* ``https://your-domain.com/api/v1/external_credentials/" +"microsoft365/callback``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:77 +msgid "" +"Find it in the Zammad admin panel under **Channels > Microsoft 365 > Connect " +"Microsoft 365 App > Your callback URL**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of new app creation in Microsoft Azure Portal\n" +"settings" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:86 +msgid "**Add API permissions**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:88 +msgid "" +"Under **API Permissions > ➕ Add a permission > Microsoft Graph > Delegated " +"permissions**, add the following:" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +#: ../settings/security/third-party/microsoft.rst:70 +msgid "OpenId permissions" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:92 +#: ../settings/security/third-party/saml.rst:85 +msgid "``email``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:93 +msgid "``offline_access``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:94 +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``openid``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:95 +msgid "``profile``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "IMAP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:98 +msgid "``IMAP.AccessAsUser.all``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "SMTP" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:101 +msgid "``SMTP.Send``" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of enabling Microsoft API permissions in Microsoft\n" +"Azure Portal" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:108 +msgid "**Admin Consent related information** (optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:112 +msgid "" +"This step is only required for tenants that require admin consent. Admin " +"consent adds another layer of security for your tenants users and allows " +"administrators to define who may share user information." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:116 +msgid "" +"Within *Enterprise applications* select your app. When creating an app " +"within *App registrations*, Microsoft will automatically also create an " +"enterprise application for you." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:120 +msgid "" +"Set *Assignment required* to ``Yes`` within the apps properties and hit " +"*Save*. This generally activates your app requesting admin consent already." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable assignment requirement" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:127 +msgid "3.1 **Tightening your app even further** (Recommended, optional)" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:131 +msgid "" +"This step is not exactly required but recommended. This step will protect " +"your tenant users from -to admins- unwanted permission changes (e.g. " +"requesting more permissions than originally noted)." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:135 +msgid "" +"It also has another benefit: You can add the email account in question " +"immediately without any administrator being forced to stepped in manually." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:139 +msgid "" +"Still within *Enterprise applications* select *Users and groups*. In this " +"section you can select specific users and / or groups (users must be direct " +"members!) that are allowed to use your app for adding mailboxes to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:144 +msgid "" +"After adding users and groups, go back to the Azure portals home and select " +"*App registrations*. Within your desired app go to *API permissions* and use " +"the *Grant admin consent for {company name}* button to generally allow " +"connecting users you previously consented." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:151 +msgid "" +"Not adding users / groups nor providing the granted admin consent right away " +"will cause Microsoft to enforce at least the first user to be requested to " +"provide a reason for the consent request. After that Microsoft will " +"automatically grant the consent for your tenant." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:156 +msgid "" +"Administrative accounts can also use the option *Consent on behalf of your " +"organization* in above mentioned permission dialogue." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "Screencast showing how to enable user based admin consent" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:164 +msgid "**Connect your Microsoft app in Zammad**" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:166 +msgid "" +"Copy your new app registration’s **Application (client) ID** and **Directory " +"(tenant) ID** (found under **Overview > Essentials**) into Zammad in the " +"admin panel, under **Channels > Microsoft 365 > Connect Microsoft 365 App**." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:171 +msgid "" +"Then, create a new client secret under **Certificates and Secrets > ➕ New " +"Client Secret** and copy that into the Zammad admin panel, as well." +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:0 +msgid "" +"Screencast demo of entering Microsoft OAuth credentials in Zammad\n" +"admin panel" +msgstr "" + +#: ../channels/microsoft365/accounts/register-app.rst:180 +msgid "" +"🍾 Congratulations! Now you’re ready to connect Microsoft 365 or Outlook " +"accounts to Zammad." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.rst:1 +msgid "" +"Secondary addresses in Microsoft 365 channels work (almost) **just like they " +"do in email channels**, so this article is lifted (almost) verbatim from :" +"doc:`here `." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:3 +msgid "" +"👀 **Secondary addresses must be added to your Microsoft account first.**" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:8 +msgid "Personal accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:6 +msgid "" +"Use the `Manage how you sign in to Microsoft `_ panel at https://account.live.com." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:16 +msgid "Hosted Exchange accounts" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:11 +msgid "In your `Exchange admin center `_:" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:13 +msgid "select a user under **recipients > mailboxes**," +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:14 +msgid "edit it (double-click or ✏️), and" +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:15 +msgid "add an an alias under **email address**." +msgstr "" + +#: ../channels/microsoft365/accounts/secondary-addresses.warning.rst:17 +msgid "" +"Contact your administrator if you don’t have access to an admin account." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + +#: ../channels/microsoft365/email-headers.rst:3 +msgid "" +"Email header manipulation in Microsoft 365 channels work **just like in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters.rst:3 +msgid "" +"Filters in Microsoft 365 channels are **just like filters in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/filters/system-filters.rst:3 +msgid "" +"System Filters in Microsoft 365 channels are **just like system filters in " +"email channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/index.rst:2 +msgid "Microsoft 365" +msgstr "" + +#: ../channels/microsoft365/index.rst:14 +msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." +msgstr "" + +#: ../channels/microsoft365/index.rst:20 +msgid "" +"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." +msgstr "" + +#: ../channels/microsoft365/index.rst:23 +msgid "" +"This documentation part does not cover :doc:`🗝 user authentication `." +msgstr "" + +#: ../channels/microsoft365/index.rst:26 +msgid "" +"If you’re already familiar with email channels, you can skip most of this—" +"but **watch out for the “Accounts” section**, which has a few extra quirks " +"due to Microsoft’s strict security measures." +msgstr "" + +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + +#: ../channels/microsoft365/settings.rst:3 +msgid "" +"Settings in Microsoft 365 channels are **just like settings in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/microsoft365/signatures.rst:3 +msgid "" +"Signatures in Microsoft 365 channels are **just like signatures in email " +"channels**, so this article is lifted verbatim from :doc:`here `." +msgstr "" + +#: ../channels/telegram.rst:2 +msgid "Telegram" +msgstr "" + +#: ../channels/telegram.rst:4 +msgid "" +"It's possible to put your Telegram bot communication into Zammad. To do so, " +"you need to follow these steps." +msgstr "" + +#: ../channels/telegram.rst:9 +msgid "" +"Your Zammad instance needs to be publicly available via HTTPS (we use " +"Telegram WebHooks)." +msgstr "" + +#: ../channels/telegram.rst:14 +msgid "" +"📎 Zammad **cannot receive file attachments larger than 20MB** in Telegram " +"messages." +msgstr "" + +#: ../channels/telegram.rst:17 +msgid "This is a hard limit imposed by the `Telegram Bot API`_." +msgstr "" + +#: ../channels/telegram.rst:22 +msgid "Register a Telegram bot app" +msgstr "" + +#: ../channels/telegram.rst:24 +msgid "" +"Register your Telegram bot via your Telegram client, see also here: https://" +"core.telegram.org/bots#3-how-do-i-create-a-bot" +msgstr "" + +#: ../channels/telegram.rst:27 +msgid "Go to BotFather" +msgstr "" + +#: ../channels/telegram.rst:None +#: ../settings/security/third-party/twitter.rst:None +msgid "inital page" +msgstr "" + +#: ../channels/telegram.rst:32 +msgid "" +"Register a new bot by using \"/newbot\" and define its name and username" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "/newbot" +msgstr "" + +#: ../channels/telegram.rst:37 +msgid "When you're all done, you will get your Telegram bot API token" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "bot has been created" +msgstr "" + +#: ../channels/telegram.rst:44 +msgid "Configure Zammad as Telegram bot" +msgstr "" + +#: ../channels/telegram.rst:46 +msgid "Go to \"Admin -> Channels -> Telegram\" and click \"Add Bot\"" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Admin -> Channels -> Telegram" +msgstr "" + +#: ../channels/telegram.rst:51 +msgid "" +"Enter your \"API Token\", your \"welcome message\" and set the incoming " +"group." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Telegram bot added" +msgstr "" + +#: ../channels/telegram.rst:56 +msgid "Done, your Zammad is now configured as a Telegram bot." +msgstr "" + +#: ../channels/telegram.rst:60 +msgid "Start using your new channel" +msgstr "" + +#: ../channels/telegram.rst:62 +msgid "" +"Go to your Telegram client, search for your new Telegram bot and start " +"writing a message." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "search for bot" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "enter a new message" +msgstr "" + +#: ../channels/telegram.rst:None +msgid "first message" +msgstr "" + +#: ../channels/telegram.rst:74 +msgid "After a few seconds a new message in Zammad appears." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "A new Ticket - the message - just reply" +msgstr "" + +#: ../channels/telegram.rst:79 +msgid "Just click on reply button (as you do it for emails) to send a reply." +msgstr "" + +#: ../channels/telegram.rst:None +msgid "Ticket reply" +msgstr "" + +#: ../channels/telegram.rst:84 +msgid "The message will appear in your Telegram client." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 +msgid "" +"Zammad supports Twitter integration, meaning you can send and receive tweets " +"and DMs just like emails!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "Twitter Ticket with draft reply" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:23 +msgid "" +"Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " +"the reply button (as you would for an email) to tweet back." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:27 +msgid "To set it up, follow the steps below:" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:29 +msgid "Apply for a `Twitter Developer account`_." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:30 +msgid "`Create a new Twitter app`_ for Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:31 +msgid "" +"Set your new app’s permissions to *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:33 +msgid "Generate a new access token & secret." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:34 +msgid "`Set up a dev environment`_ for the Account Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:35 +msgid "Add your new Twitter app in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:36 +msgid "Add your Twitter account in Zammad." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:37 +msgid "" +"Configure filters for creating new tickets based on **#tags** and " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:40 +msgid "Read on for details about each step." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:43 +msgid "1. Apply for a Twitter Developer account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "Twitter Developer account: Welcome page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:49 +msgid "" +"This welcome page is displayed after completing the application for a " +"Developer account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:52 +msgid "" +"You will need a regular Twitter account with a verified phone number to " +"apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:55 +msgid "" +"During the application process, you will be asked to **Describe in your own " +"words what you are building**. You may use the answer below::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:67 +msgid "2. Create a new Twitter app for Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "Twitter Developer account: Create app page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:73 +msgid "" +"To create a new app, select **Apps** under your user menu, then click " +"**Create an app**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:76 +msgid "" +"Once you have finished setting up your Developer account, use it to `create " +"a new Twitter app`_. The following fields are **required:**" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:82 +msgid "App name" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:81 +msgid "" +"Must be unique *across all of Twitter.* No other developer account may " +"create an app with the same name." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Application description" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:85 +msgid "Anything is fine here." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "Website URL" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:88 +msgid "The URL of your Zammad instance." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:94 +msgid "Callback URLs" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:91 +msgid "" +"``https:///api/v1/external_credentials/twitter/callback``" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:93 +msgid "" +"This URL is also visible in the **Connect Twitter App** dialog of your " +"Zammad admin settings panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:100 +msgid "Tell us how this app will be used" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:97 +msgid "Anything is fine here. We suggest the following::" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:103 +msgid "3. Set your new app’s permissions" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App permissions page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:109 +msgid "Select *Read, write, and access direct messages.*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:112 +msgid "4. Generate a new access token & secret" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:0 +msgid "Twitter Developer account: App keys and tokens page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:118 +msgid "You will need all four keys/tokens later, so don’t close this tab." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:121 +msgid "5. Set up a dev environment" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:123 +msgid "" +"After creating your app, `set up a dev environment`_ for the Account " +"Activity API." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "Twitter Developer account: Dev environments page" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:130 +msgid "" +"Name it whatever you like (*e.g.,* ``zammad``). You will need the label " +"later, so don’t forget it." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:134 +msgid "6. Add your new Twitter app in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "Zammad: Configure Twitter app" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:140 +msgid "" +"Add your new Twitter app under **Channels > Twitter** in the admin settings " +"panel. You will need the keys, tokens, and dev environment label from Steps " +"4 and 5." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:145 +msgid "7. Add your Twitter account in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "Zammad: Add Twitter account" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:151 +msgid "" +"Click **Add Account** under **Channels > Twitter** in the admin settings " +"panel." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "Twitter: Authorize Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:158 +msgid "" +"You will be redirected to Twitter and asked to authorize Zammad to access " +"your account." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:162 +msgid "8. Configure filters" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "Zammad: Configure Twitter accounts" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:168 +msgid "" +"Set up filters to automatically create new tickets based on **#tags** or " +"**@mentions**." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:171 +msgid "" +"That’s it! Now, incoming tweets and DMs will be automatically turned into " +"Zammad tickets." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + +#: ../channels/web.rst:2 +msgid "Web" +msgstr "" + +#: ../channels/web.rst:4 +msgid "" +"The web channel mainly affects your customers' using the web interface. " +"These settings allow you to restrict your customers ticket creation." +msgstr "" + +#: ../channels/web.rst:9 +msgid "" +":doc:`/system/core-workflows` allow even further restrictions and actions if " +"you need them. 🤓" +msgstr "" + +#: ../channels/web.rst:None +msgid "The web channel settings page" +msgstr "" + +#: ../channels/web.rst:17 +msgid "Settings affecting your customer" +msgstr "" + +#: ../channels/web.rst:29 +msgid "Enable Ticket creation" +msgstr "" + +#: ../channels/web.rst:20 +msgid "" +"You can forbid customers to create tickets via the web interface. This will " +"remove the \"➕\" button on the lower left." +msgstr "" + +#: ../channels/web.rst:23 ../manage/public-links.rst:0 +#: ../system/objects/types.rst:0 +msgid "Default: ``yes``" +msgstr "" + +#: ../channels/web.rst:27 +msgid "This does not forbid updating existing tickets via UI." +msgstr "" + +#: ../channels/web.rst:41 +msgid "Group selection for Ticket creation" +msgstr "" + +#: ../channels/web.rst:32 +msgid "" +"By default your customers may create tickets in all groups. As this may be " +"an issue, especially when having several support levels or internal groups, " +"you can always select a set of groups you want to be available." +msgstr "" + +#: ../channels/web.rst:37 +msgid "Default: ``-``" +msgstr "" + +#: ../channels/web.rst:39 +msgid "**🤓 This does not affect your agents**" +msgstr "" + +#: ../channels/web.rst:41 +msgid "Agents are affected by :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../channels/web.rst:44 +msgid "Global settings affecting *all* users" +msgstr "" + +#: ../channels/web.rst:59 +msgid "Tab behavior after ticket creation" +msgstr "" + +#: ../channels/web.rst:47 +msgid "" +"This setting allows administrators to provide a default behavior of Zammad's " +"tab *after* ticket update." +msgstr "" + +#: ../channels/web.rst:50 +msgid "Default: ``Stay on tab``" +msgstr "" + +#: ../channels/web.rst:52 +msgid "**Users can always overrule**" +msgstr "" + +#: ../channels/web.rst:54 +msgid "" +"If your user decides to select a different tab behavior on any ticket, this " +"action will be the new default behavior for that user." +msgstr "" + +#: ../channels/web.rst:57 +msgid "Zammad remembers the decision of the user. 💾" +msgstr "" + +#: ../channels/web.rst:0 +msgid "Ticket zoom with tab behavior to choose for the user" +msgstr "" + +#: ../index.rst:6 +msgid "Manage" +msgstr "" + +#: ../index.rst:31 +msgid "Channels" +msgstr "" + +#: ../index.rst:59 +msgid "API (System-Admin Documentation)" +msgstr "" + +#: ../index.rst:59 ../settings/system/index.rst:2 +msgid "System" +msgstr "" + +#: ../index.rst:79 +msgid "Misc" +msgstr "" + +#: ../index.rst:2 +msgid "Zammad - Documentation for administrators" +msgstr "" + +#: ../manage/calendars.rst:2 +msgid "Calendars" +msgstr "" + +#: ../manage/calendars.rst:4 +msgid "A calendar is required to:" +msgstr "" + +#: ../manage/calendars.rst:6 +msgid "automate ticket escalations," +msgstr "" + +#: ../manage/calendars.rst:7 +msgid "generate reports that only capture activity during business hours, or" +msgstr "" + +#: ../manage/calendars.rst:8 +msgid "set up time-sensitive triggers." +msgstr "" + +#: ../manage/calendars.rst:10 +msgid "" +"Define a \"standard\"-calendar which system-wide is valid. Only in the " +"specified business hours, escalation notifications are sent to agents." +msgstr "" + +#: ../manage/calendars.rst:13 +msgid "" +"If you have customers for which you have to comply with different customer " +"business hours, you can create several calendars. The allocation to the " +"customer tickets can be adjusted via the SLAs." +msgstr "" + +#: ../manage/calendars.rst:18 +msgid "And this is what it looks like:" +msgstr "" + +#: ../manage/calendars.rst:22 +msgid "All created calendars are displayed in the overview." +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "New Calendar" +msgstr "" + +#: ../manage/calendars.rst:25 +msgid "" +"Here you can create a new calendar if agents or customers belong to another " +"time zone." +msgstr "" + +#: ../manage/calendars.rst:28 +msgid "" +"Just push the delete-button to delete this specific calendar - all SLAs " +"assigned to this calendar are automatically assigned to the default calendar." +msgstr "" + +#: ../manage/calendars.rst:33 +msgid "Set as Default" +msgstr "" + +#: ../manage/calendars.rst:32 +msgid "" +"Pressing this button sets this calendar as the default calendar for the " +"entire system." +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "Edit" +msgstr "" + +#: ../manage/calendars.rst:36 +msgid "" +"Via this button you get to the edit-mask (same mask as in \"New Calendar\"):" +msgstr "" + +#: ../manage/calendars.rst:40 +msgid "" +"--> determine a name, a time-zone, the business hours to be used for this " +"calendar and special holidays. In addition, you can subscribe to the " +"iCalendar, which will automatically load all holidays from Google (updated " +"once a day) ... and you can add a note." +msgstr "" + +#: ../manage/groups/access-levels.rst:2 +msgid "Group Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:4 +msgid "" +"When assigning an agent to a :doc:`group `, Zammad " +"gives you fine-grained control over what actions that agent can perform " +"within it:" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "The group access level setting in the Edit User dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:13 +msgid "Use the group access table to grant per-group privileges." +msgstr "" + +#: ../manage/groups/access-levels.rst:15 +msgid "Within each group, the different access levels allow an agent to..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "READ" +msgstr "" + +#: ../manage/groups/access-levels.rst:17 +msgid "...view tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CREATE" +msgstr "" + +#: ../manage/groups/access-levels.rst:18 +msgid "...create new tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "CHANGE" +msgstr "" + +#: ../manage/groups/access-levels.rst:19 +msgid "...modify existing tickets" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "OVERVIEW" +msgstr "" + +#: ../manage/groups/access-levels.rst:20 +msgid "...see ticket overviews (but not ticket details)" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "FULL" +msgstr "" + +#: ../manage/groups/access-levels.rst:21 +msgid "" +"...all of the above **and be assigned / receive notifications for tickets**" +msgstr "" + +#: ../manage/groups/access-levels.rst:26 +msgid "" +"🔔 **Full group access also enables notifications for that group’s tickets.**" +msgstr "" + +#: ../manage/groups/access-levels.rst:29 +msgid "Setting Access Levels" +msgstr "" + +#: ../manage/groups/access-levels.rst:31 +msgid "There are two ways to define an agent’s per-group access levels:" +msgstr "" + +#: ../manage/groups/access-levels.rst:33 +msgid "Directly, in the :ref:`Edit User dialog `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"Screencast showing a user being assigned specific group rights directly " +"within the user." +msgstr "" + +#: ../manage/groups/access-levels.rst:40 +msgid "Simply set your access levels right on the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:42 +msgid "" +"Implicitly, by :ref:`editing a user’s roles `" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 ../manage/roles/agent-permissions.rst:0 +msgid "Group access table in Edit Role dialog" +msgstr "" + +#: ../manage/groups/access-levels.rst:49 +msgid "First, set your access levels on a role..." +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "Screencast showing a user receiving further roles" +msgstr "" + +#: ../manage/groups/access-levels.rst:56 +msgid "...then, add that role to the target user." +msgstr "" + +#: ../manage/groups/access-levels.rst:58 +msgid "" +"⚖️ **We recommend choosing one or the other**; things can get confusing if " +"you use both at the same time." +msgstr "" + +#: ../manage/groups/access-levels.rst:61 +msgid "" +"So which one is right for you? *Whichever one is less work.* If you’re " +"trying to assign multiple agents to the same group with the same access " +"levels, create a role for them to share—that’s what roles are for!" +msgstr "" + +#: ../manage/groups/access-levels.rst:67 +msgid "Examples" +msgstr "" + +#: ../manage/groups/access-levels.rst:77 +msgid "“The Standard Issue”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Full\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:75 +msgid "" +"When a system only has one group, this is the default access level assigned " +"to all agents. Unless you have special needs in mind, this is the way to go." +msgstr "" + +#: ../manage/groups/access-levels.rst:87 +msgid "“The Supervisor”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "" +"The group access table, checked \"Read\", \"Create\", \"Change\", and " +"\"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:85 +msgid "" +"Agents with all permissions except for “full” **cannot be assigned " +"tickets**. Otherwise, their privileges are identical to agents with “full” " +"access. Great for letting other people do the real work." +msgstr "" + +#: ../manage/groups/access-levels.rst:97 +msgid "“The Meddler”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Read\", \"Change\", and \"Overview" +msgstr "" + +#: ../manage/groups/access-levels.rst:95 +msgid "" +"Agents with “read”, “change”, and “overview” access can do everything except " +"create tickets or be assigned to them. Great for getting involved in other " +"people’s business." +msgstr "" + +#: ../manage/groups/access-levels.rst:106 +msgid "“The Intern”" +msgstr "" + +#: ../manage/groups/access-levels.rst:0 +msgid "The group access table, checked \"Create\"" +msgstr "" + +#: ../manage/groups/access-levels.rst:105 +msgid "" +"Agents with only “create” access can do just that, and nothing else—once " +"they hit **Save**, they’ll never see that ticket again. Great for taking " +"phone calls for someone more important than you." +msgstr "" + +#: ../manage/groups/index.rst:28 ../manage/macros.rst:36 +#: ../manage/slas/index.rst:94 ../manage/trigger.rst:30 +#: ../manage/webhook.rst:45 ../system/core-workflows.rst:30 +#: ../system/objects.rst:32 +msgid "Learn more" +msgstr "" + +#: ../manage/groups/index.rst:2 ../manage/macros/how-do-they-work.rst:0 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Groups" +msgstr "" + +#: ../manage/groups/index.rst:4 +msgid "" +"This is the group management area. From here you can edit existing groups " +"and add new groups." +msgstr "" + +#: ../manage/groups/index.rst:7 +msgid "" +"Groups in Zammad are similar to working groups that deal with different " +"topics within a company. For example, the tickets relevant to the sales " +"department might be available in the *Sales* group, while the tickets for " +"the support department might be available in the *Support* group. These are " +"just examples; how you structure your groups is up to you." +msgstr "" + +#: ../manage/groups/index.rst:13 +msgid "" +"Tickets enter Zammad through various channels (e.g. via email) and are then " +"sorted into these groups. The tickets (cases) are thus made available to the " +"agents responsible for the group. Each ticket can only belong to one group, " +"and you can decide via **access levels** (see below) what access your agents " +"have in each group. For example, you might want set up a group *Management* " +"for confidential tickets; with access levels, you can configure that only a " +"few select agents will have access to these tickets." +msgstr "" + +#: ../manage/groups/index.rst:21 +msgid "" +"For an additional way to categorize tickets, have a look at :doc:`/manage/" +"tags`." +msgstr "" + +#: ../manage/groups/index.rst:25 +msgid "" +"Zammad users are global to the whole instance. Restriction to specific " +"groups is not possible." +msgstr "" + +#: ../manage/groups/index.rst:35 +msgid "If the *Group* field does not appear in the ticket view, ensure that:" +msgstr "" + +#: ../manage/groups/index.rst:37 +msgid "you have created more than one group" +msgstr "" + +#: ../manage/groups/index.rst:38 +msgid "the current user has \"change\" permissions to more than one group" +msgstr "" + +#: ../manage/groups/index.rst:40 +msgid "" +"This is necessary because Zammad automatically hides selection fields with " +"only one option." +msgstr "" + +#: ../manage/groups/settings.rst:2 +msgid "Group Settings" +msgstr "" + +#: ../manage/groups/settings.rst:4 +msgid "" +"Click on a group to edit it, or click on *New group* to create a new group." +msgstr "" + +#: ../manage/groups/settings.rst:None +msgid "Screenshot showing Zammad's group management" +msgstr "" + +#: ../manage/groups/settings.rst:9 +msgid "" +"No matter if you're going to edit or create a new group, each group comes " +"with the following settings you can adjust as needed." +msgstr "" + +#: ../manage/groups/settings.rst:13 +msgid "" +"This is the name your agents (and customers when using :doc:`/channels/web`) " +"will see within the Zammad-UI." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "Assignment timeout" +msgstr "" + +#: ../manage/groups/settings.rst:17 +msgid "" +"The time in minutes after which the ticket's ownership will revert back to " +"*unassigned* after the assigned agent hasn't worked on the ticket." +msgstr "" + +#: ../manage/groups/settings.rst:22 +msgid "This timeout does not take any working hours in account." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "Follow-up possible" +msgstr "" + +#: ../manage/groups/settings.rst:25 +msgid "" +"This option allows you to decide how Zammad should react if a customer " +"replies to a closed ticket (no matter if by e.g. email or UI)." +msgstr "" + +#: ../manage/groups/settings.rst:29 ../manage/groups/settings.rst:50 +msgid "yes" +msgstr "" + +#: ../manage/groups/settings.rst:29 +msgid "The ticket will be reopened. This is the default value." +msgstr "" + +#: ../manage/groups/settings.rst:33 +msgid "do not reopen Ticket but create new Ticket" +msgstr "" + +#: ../manage/groups/settings.rst:32 +msgid "" +"The ticket will remain closed and Zammad will create a new ticket instead. " +"The new ticket contains the customers reply only." +msgstr "" + +#: ../manage/groups/settings.rst:42 +msgid "do not reopen ticket after certain time but create new ticket" +msgstr "" + +#: ../manage/groups/settings.rst:36 +msgid "" +"The ticket can be reopened unless the specified number of days *after last " +"ticket closure* has been exceeded. If the time limit is exceeded, Zammad " +"will create a new ticket instead of reopening." +msgstr "" + +#: ../manage/groups/settings.rst:40 +msgid "" +"Choosing this option will provide the option *Reopening time in days* which " +"requires you to provide the number of days you want Zammad to wait until it " +"creates new tickets." +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "Assign follow-ups" +msgstr "" + +#: ../manage/groups/settings.rst:45 +msgid "" +"This setting allows you to decide if, upon a reopen of a ticket, the last " +"assigned owner should stay assigned or if Zammad should reset the owner to " +"nobody." +msgstr "" + +#: ../manage/groups/settings.rst:50 +msgid "" +"The ticket will remain to the last agent who owned it. This is the default " +"value" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "no" +msgstr "" + +#: ../manage/groups/settings.rst:53 +msgid "The owner assignment of the ticket will be removed." +msgstr "" + +#: ../manage/groups/settings.rst:56 +msgid "" +"Select which sender's email address Zammad will use outbound for replying on " +"a ticket in this group." +msgstr "" + +#: ../manage/groups/settings.rst:59 +msgid "**You don't have an email address configured yet?**" +msgstr "" + +#: ../manage/groups/settings.rst:61 +msgid "Please configure an email based channel before here" +msgstr "" + +#: ../manage/groups/settings.rst:63 +msgid ":doc:`Channels → Email `" +msgstr "" + +#: ../manage/groups/settings.rst:64 +msgid ":doc:`Channels → Microsoft 365 `" +msgstr "" + +#: ../manage/groups/settings.rst:65 +msgid ":doc:`Channels → Google `" +msgstr "" + +#: ../manage/groups/settings.rst:67 +msgid "and come back afterwards." +msgstr "" + +#: ../manage/groups/settings.rst:72 +msgid "Signature" +msgstr "" + +#: ../manage/groups/settings.rst:70 +msgid "" +"Choose which :doc:`signature ` to use when " +"replying to tickets in this group. Leaving this option unset will send " +"emails without any signature." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Shared Drafts" +msgstr "" + +#: ../manage/groups/settings.rst:75 +msgid "" +"Shared drafts allows your agents to share ticket drafts (for new and " +"existing tickets) with their colleagues. By default this setting is enabled, " +"disable it if you don't want your agents to use this function." +msgstr "" + +#: ../manage/groups/settings.rst:79 +msgid "Learn more about `shared drafts in our user documentation`_." +msgstr "" + +#: ../manage/groups/settings.rst:85 +msgid "" +"An internal note about the group that is only visible to people who can " +"access the group management area." +msgstr "" + +#: ../manage/groups/settings.rst:89 +msgid "" +"Don't need the group any more? If you can't or don't want to recycle " +"(rename) the group, you can also set it to inactive. Agents and customers " +"will no longer be able to see the group and thus can't add, update or read " +"it's tickets." +msgstr "" + +#: ../manage/groups/settings.rst:96 +msgid "As of now groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:100 +msgid "" +"Please keep in mind that you still can route tickets into these groups. This " +"is potentially dangerous, make sure the group is no longer part of email " +"filters or a destination group." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "Screenshot showing how a group configuration can look like." +msgstr "" + +#: ../manage/groups/settings.rst:109 +msgid "A sample configuration of a group." +msgstr "" + +#: ../manage/knowledge-base.rst:2 +msgid "Knowledge Base" +msgstr "" + +#: ../manage/knowledge-base.rst:4 +msgid "" +"Publish your own library of FAQs, how-tos, internal SOPs and more with the " +"**knowledge base**." +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "Sample Knowledge Base Index" +msgstr "" + +#: ../manage/knowledge-base.rst:11 +msgid "See a live demo at https://support.zammad.com/help." +msgstr "" + +#: ../manage/knowledge-base.rst:13 +msgid "This document describes how to ⚙ **configure** the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:15 +msgid "" +"For details on how to ✍️ **use and edit** it, please refer to the `Zammad " +"user documentation`_." +msgstr "" + +#: ../manage/knowledge-base.rst:18 +msgid "" +"By default, only admin users are permitted to create, edit, and manage " +"knowledge base articles. See :doc:`roles/index` for details on how to grant " +"write access to agents or other users." +msgstr "" + +#: ../manage/knowledge-base.rst:25 +msgid "" +"The knowledge base will not appear in the main menu until it has been " +"enabled in the admin panel." +msgstr "" + +#: ../manage/knowledge-base.rst:29 +msgid "Features" +msgstr "" + +#: ../manage/knowledge-base.rst:31 +msgid "🌍 Multi-language support" +msgstr "" + +#: ../manage/knowledge-base.rst:32 +msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)" +msgstr "" + +#: ../manage/knowledge-base.rst:33 +msgid "🔍 Full text search" +msgstr "" + +#: ../manage/knowledge-base.rst:34 +msgid "📅 Scheduled publishing" +msgstr "" + +#: ../manage/knowledge-base.rst:35 +msgid "📎 File attachments" +msgstr "" + +#: ../manage/knowledge-base.rst:36 +msgid "" +"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**" +msgstr "" + +#: ../manage/knowledge-base.rst:37 +msgid "🖼️ Rich text editor + embedded images" +msgstr "" + +#: ../manage/knowledge-base.rst:40 ../system/integrations/github.rst:16 +#: ../system/integrations/gitlab.rst:16 +msgid "Setup" +msgstr "" + +#: ../manage/knowledge-base.rst:42 +msgid "" +"To enable the knowledge base, first select the languages/locales you wish to " +"publish in:" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "Knowledge Base: Initial setup" +msgstr "" + +#: ../manage/knowledge-base.rst:49 +msgid "" +"You must choose at least one. (Don’t worry, you can always change them " +"later!)" +msgstr "" + +#: ../manage/knowledge-base.rst:52 +msgid "" +"Read on for details about each section of the knowledge base configuration." +msgstr "" + +#: ../manage/knowledge-base.rst:55 +msgid "Theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "Knowledge Base: Configure theme" +msgstr "" + +#: ../manage/knowledge-base.rst:61 +msgid "🎨 Customize the appearance of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon & Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:64 +msgid "" +"Applies to all **category & article** entries in knowledge base menus, as " +"well as hyperlinks in articles." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Color" +msgstr "" + +#: ../manage/knowledge-base.rst:68 +msgid "Applies to the area surrounding the search bar." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Header Link Color" +msgstr "" + +#: ../manage/knowledge-base.rst:71 +msgid "" +"Defines the color of the header links to use. Make sure that this color has " +"a proper contrast to *Header Color*." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Show Feed Icon" +msgstr "" + +#: ../manage/knowledge-base.rst:75 +msgid "" +"You can enable Zammad to provide RSS feed URLs in both internal and public " +"knowledge base. With this option being active, Zammad will provide you up to " +"two RSS links:" +msgstr "" + +#: ../manage/knowledge-base.rst:79 +msgid "a general RSS feed of the whole knowledge base (top level)" +msgstr "" + +#: ../manage/knowledge-base.rst:80 +msgid "" +"a category specific RSS feed of the category you're in (also applies to " +"answers you're viewing)" +msgstr "" + +#: ../manage/knowledge-base.rst:83 +msgid "This setting by default is set to ``no``." +msgstr "" + +#: ../manage/knowledge-base.rst:87 +msgid "" +"Your agents will receive special RSS feed URLs with **access tokens**. " +"Agents can always renew these. Keep in mind that sharing these URLs with " +"third parties may provide access to **internal** answers!" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Icon Set" +msgstr "" + +#: ../manage/knowledge-base.rst:92 +msgid "" +"Defines the selection of icons that may be used when creating/editing " +"categories." +msgstr "" + +#: ../manage/knowledge-base.rst:95 +msgid "" +"Each category in the knowledge base *must* be given an icon. Icons appear " +"prominently in the main menu, like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Knowledge Base: Icons" +msgstr "" + +#: ../manage/knowledge-base.rst:104 +msgid "" +"🤦‍♀️ Re-assigning icons on all of your categories is tedious work. It's " +"advisable to explore your options early to avoid having to change your mind " +"down the road." +msgstr "" + +#: ../manage/knowledge-base.rst:109 +msgid "Languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "Knowledge Base: Configure languages" +msgstr "" + +#: ../manage/knowledge-base.rst:115 +msgid "🌍 Add or remove locales, or reassign the default." +msgstr "" + +#: ../manage/knowledge-base.rst:117 +msgid "" +"The knowledge base will automatically display the language matching each " +"visitor’s locale. Visitors may always manually switch to another language " +"via a dropdown menu in the footer." +msgstr "" + +#: ../manage/knowledge-base.rst:121 +msgid "" +"The default locale is displayed when the visitor’s locale is not supported." +msgstr "" + +#: ../manage/knowledge-base.rst:123 +msgid "" +"Articles that have not yet been translated into a given language will be " +"hidden from that locale." +msgstr "" + +#: ../manage/knowledge-base.rst:127 +msgid "Public Menu" +msgstr "" + +#: ../manage/knowledge-base.rst:129 +msgid "" +"Use this section to unify the knowledge base with your own website’s main " +"navigation. Entries added here will appear in the knowledge base like so:" +msgstr "" + +#: ../manage/knowledge-base.rst:None +msgid "Knowledge Base: Public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:136 +msgid "" +"Zammad will provide a list of the current set links per knowledge base " +"language. If you're missing a language, you'll have to add the language up " +"front." +msgstr "" + +#: ../manage/knowledge-base.rst:139 +msgid "You can adjust every URL on language level." +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "Knowledge Base: Configure public menu" +msgstr "" + +#: ../manage/knowledge-base.rst:145 +msgid "" +"🧭 Customize the nav menu that appears in the header of the knowledge base." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Arranging URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:148 +msgid "" +"By clicking on \"Edit\", Zammad allows you to add, update, re-arrange or " +"remove URLs from either your public header menu or public footer menu." +msgstr "" + +#: ../manage/knowledge-base.rst:152 ../manage/public-links.rst:53 +#: ../manage/time-accounting.rst:84 ../manage/time-accounting.rst:97 +#: ../system/maintenance.rst:31 +msgid "Title" +msgstr "" + +#: ../manage/knowledge-base.rst:152 +msgid "This is the URL title that's being displayed to your users." +msgstr "" + +#: ../manage/knowledge-base.rst:155 ../manage/webhook/log.rst:19 +#: ../system/integrations/elasticsearch.rst:57 +msgid "URL" +msgstr "" + +#: ../manage/knowledge-base.rst:155 +msgid "The actual URL the user is going to open upon clicking." +msgstr "" + +#: ../manage/knowledge-base.rst:159 +msgid "Target" +msgstr "" + +#: ../manage/knowledge-base.rst:158 +msgid "" +"Allows you to tell your users browser to open the URL in a new tab. By " +"default your user would leave the knowledge base page if not set." +msgstr "" + +#: ../manage/knowledge-base.rst:162 +msgid "" +"If you tick the delete field, the URL will be removed from the menu upon " +"pressing on the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:174 +msgid "Change URLs position" +msgstr "" + +#: ../manage/knowledge-base.rst:166 +msgid "" +"Use ☰ to drag & drop the URLs in question to the new desired position. Your " +"changes will be saved with pressing the \"Submit\" button." +msgstr "" + +#: ../manage/knowledge-base.rst:0 +msgid "Screencast showing the repositioning of URLs" +msgstr "" + +#: ../manage/knowledge-base.rst:173 +msgid "" +"Re-arranging URL positions works for the header menu just as the footer menu" +msgstr "" + +#: ../manage/knowledge-base.rst:177 +msgid "Custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:179 +msgid "This feature is only available on **self-hosted** instances." +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "Knowledge Base: Configure custom URL" +msgstr "" + +#: ../manage/knowledge-base.rst:185 +msgid "📍 Relocate the knowledge base to the URL of your choosing." +msgstr "" + +#: ../manage/knowledge-base.rst:187 +msgid "" +"By default, the knowledge base will appear at the same domain as your Zammad " +"instance, under ``/help``." +msgstr "" + +#: ../manage/knowledge-base.rst:190 +msgid "" +"If you wish to customize where it can be accessed, enter your desired URL " +"here and configure your web server as described (instructions provided for " +"Apache and NGINX only)." +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "Knowledge Base: Delete knowledge base" +msgstr "" + +#: ../manage/knowledge-base.rst:201 +msgid "🗑️ Permanently delete the knowledge base and all the articles within it." +msgstr "" + +#: ../manage/knowledge-base.rst:203 +msgid "" +"Use this panel to delete the knowledge base. If you wish to unpublish it " +"without deleting all its content, simply disable it via the toggle button at " +"the top of the window instead." +msgstr "" + +#: ../manage/macros.rst:2 +msgid "Macros" +msgstr "" + +#: ../manage/macros.rst:4 +msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgstr "" + +#: ../manage/macros.rst:6 +msgid "" +"If you find yourself making the same changes to lots of tickets (*e.g.,* " +"close-and-tag-as-spam or reassign-to-another-group), you can store those " +"changes in a macro for easy access:" +msgstr "" + +#: ../manage/macros.rst:15 +msgid "Example macros within a ticket detail view." +msgstr "" + +#: ../manage/macros.rst:15 +msgid "" +"Choose from the macros **Close & Tag as Spam**, **Move to RMA**, and **Reply " +"& Close & Tag as Banana**." +msgstr "" + +#: ../manage/macros.rst:18 +msgid "" +"You can also apply macros in bulk (*i.e.,* to many tickets all at once) via " +"the *Overviews* page:" +msgstr "" + +#: ../manage/macros.rst:26 +msgid "Example macros within an overview (bulk operation)." +msgstr "" + +#: ../manage/macros.rst:26 +msgid "" +"Select your desired tickets, then click-and-drag to apply a macro to all of " +"them." +msgstr "" + +#: ../manage/macros.rst:29 +msgid "You can create or edit macros on the Macros page of the admin panel:" +msgstr "" + +#: ../manage/macros.rst:None +msgid "Screenshot of “Macros” page in admin panel" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:2 +#: ../manage/slas/how-do-they-work.rst:2 +#: ../manage/trigger/how-do-they-work.rst:2 +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:4 +msgid "" +"Macros are made up of **actions** (changes to a ticket). You can add as many " +"actions to a macro as you want." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:7 +msgid "" +"There are also a few other settings that affect who can use a macro or how " +"it behaves." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:10 +msgid "Creating Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:None +msgid "Screenshot showing different possible actions for macros." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 ../manage/templates.rst:38 +#: ../manage/trigger/how-do-they-work.rst:66 +msgid "Actions" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:18 +msgid "You can create actions to:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:20 +msgid "set ticket attributes (priority, state, group, etc.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:21 +msgid "add new notes to a ticket" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:23 +msgid "There are **no** actions for:" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:25 +msgid "sending a reply to the customer" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:27 +msgid "" +"Unlike triggers, the scheduler, and text modules, macro actions do **not** " +"support the use of :doc:`/system/variables`." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:31 +msgid "" +"If the ticket is missing a required attribute and the macro doesn’t set it, " +"then **no actions will be applied**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:0 +msgid "Once completed..." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:36 +msgid "" +"After running this macro, should Zammad remain on the current tab, close it, " +"or automatically switch to the next ticket? (Does not apply when running " +"macros “in bulk”.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:41 +msgid "" +"What should other Zammad admins know about this macro? (Visible only via the " +"“Edit: Macro” dialog, Rails console, and API.)" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:45 +msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:48 +msgid "Choose “inactive” to disable this macro without deleting it." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:51 +msgid "Managing Macros" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:53 +msgid "" +"You can delete or even clone existing macros in the Admin Panel under " +"**Manage > Macros**." +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"Screencast showing the creation of a new macro via cloning and its removal" +msgstr "" + +#: ../manage/macros/how-do-they-work.rst:60 +msgid "" +"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"created." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:2 +#: ../manage/slas/learn-by-example.rst:2 +#: ../manage/trigger/learn-by-example.rst:2 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"one-click actions you can set up using macros." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:9 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/macros/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:14 +msgid "" +"If you deal with a lot of spam, you could set up a macro that applies the " +"following changes to a ticket:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:17 +msgid "closed" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2 +msgid "Tags" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:18 +msgid "add ``spam``" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:19 +#: ../manage/macros/learn-by-example.rst:37 +#: ../misc/object-conditions/basics.rst:0 +msgid "current user" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing spam macro configuration and behavior" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:26 +msgid "" +"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up " +"unwanted tickets." +msgstr "" + +#: ../manage/macros/learn-by-example.rst:29 +msgid "" +"If you want to set a ticket’s state to *pending reminder*, it’s usually a " +"two-step process—first select the state, then select a date. To always set a " +"reminder for the same, fixed amount of time (say, seven days later), you can " +"bundle the whole change into a macro:" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:34 +msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:35 +msgid "pending reminder" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Pending Till" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:36 +msgid "relative / 7 / days" +msgstr "" + +#: ../manage/macros/learn-by-example.rst:0 +msgid "Screencast showing postpone macro configuration and behavior" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via CSV import" +msgstr "" + +#: ../manage/organizations/index.rst:16 +msgid "via REST API" +msgstr "" + +#: ../manage/organizations/index.rst:2 +msgid "Organizations" +msgstr "" + +#: ../manage/organizations/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, organizations can be " +"managed individually or in bulk." +msgstr "" + +#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +msgid "Creating and editing users directly in the Admin Panel" +msgstr "" + +#: ../manage/organizations/index.rst:12 +msgid "" +"The simplest way to manage organizations is directly in the Admin Panel." +msgstr "" + +#: ../manage/organizations/index.rst:14 +msgid "Learn more about managing organizations..." +msgstr "" + +#: ../manage/organizations/index.rst:23 +msgid "😲 **Technical Limitations**" +msgstr "" + +#: ../manage/organizations/index.rst:25 +msgid "" +"Organizations currently cannot be removed. The only exception is Zammad's :" +"doc:`/system/data-privacy` function." +msgstr "" + +#: ../manage/organizations/index.rst:27 +msgid "" +"Unlike users, agents cannot just create new organizations. Check the :doc:" +"`permission reference ` to learn more." +msgstr "" + +#: ../manage/organizations/index.rst:30 +msgid "" +"Because of how organization references work with users, external syncs like " +"LDAP or Exchange *do not* support organization mapping." +msgstr "" + +#: ../manage/organizations/index.rst:35 +msgid "This is relevant to you? Consider domain based assignments." +msgstr "" + +#: ../manage/organizations/index.rst:37 +msgid "🥵 **BIG organizations can cause performance issues**" +msgstr "" + +#: ../manage/organizations/index.rst:39 +msgid "" +"Organizations with many members can cause a fairly high system load in some " +"situations. This especially affects organizations whose members run many " +"updates, for example ticket creations or frequent communication. A lot of " +"linked data syncs may cause an overhead." +msgstr "" + +#: ../manage/organizations/index.rst:44 +msgid "Proceed with caution." +msgstr "" + +#: ../manage/organizations/index.rst:49 +msgid "Reference Guide: Organization Details" +msgstr "" + +#: ../manage/organizations/index.rst:51 +msgid "" +"Most of the attributes you can set on organizations are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "" +"The edit organization dialog, showing the various organization detail fields" +msgstr "" + +#: ../manage/organizations/index.rst:59 +msgid "User details can be set in the **New/Edit Organization** dialog." +msgstr "" + +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 +msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +msgstr "" + +#: ../manage/organizations/index.rst:63 +msgid "" +"In most cases, agents can, too (using the `ticket pane`_ or organization " +"detail page)." +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "📢 Shared Organization" +msgstr "" + +#: ../manage/organizations/index.rst:70 +msgid "" +"If you set this option to ``yes``, all organization members will be able to " +"**view** and **update** tickets of their organizational members in addition " +"to their own." +msgstr "" + +#: ../manage/organizations/index.rst:74 +msgid "" +"Setting this option to yes also provides access to overviews being available " +"to shared organizations only. Learn more on :doc:`/manage/overviews`." +msgstr "" + +#: ../manage/organizations/index.rst:78 +msgid "The default value on creation dialogues is ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:82 +msgid "" +"This can cause serious issues if you have e.g.human resources working in the " +"same Zammad instance. Shared organizations usually are relevant for Support " +"companies with fairly big customers and support contingents." +msgstr "" + +#: ../manage/organizations/index.rst:88 +msgid "" +"Sharing organizations don't just affect customers, however, if you want to " +"provide ticket access to agents, please see the :ref:`permission-guide`." +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "" +"Screenshot showing \"My Organization Tickets\" overview with tickets\n" +"belonging to all organization members" +msgstr "" + +#: ../manage/organizations/index.rst:97 +msgid "" +"Members of shared organization have access to organization based overviews" +msgstr "" + +#: ../manage/organizations/index.rst:110 +msgid "🗄️ Domain based assignment" +msgstr "" + +#: ../manage/organizations/index.rst:100 +msgid "" +"Activating domain based assignment will cause Zammad to automatically add " +"newly created users to said organization. This can greatly reduce your " +"maintenance effort and is seen as workaround for not being able to map " +"organizations via LDAP." +msgstr "" + +#: ../manage/organizations/index.rst:105 +msgid "The default value on creation dialogues is ``no``" +msgstr "" + +#: ../manage/organizations/index.rst:109 +msgid "" +"Domain based assignment only works for *newly created* users and has no " +"effect on existing users." +msgstr "" + +#: ../manage/organizations/index.rst:121 +msgid "🌐 Domain" +msgstr "" + +#: ../manage/organizations/index.rst:113 +msgid "" +"Add the email domain of the organization with this option. It's being used " +"on user creation to determine the assignment. This option belongs to domain " +"based assignment and is required if set to ``yes``." +msgstr "" + +#: ../manage/organizations/index.rst:119 +msgid "" +"At the time Zammad allows *one* domain per organization. You may also want " +"to ensure to not use free mailer domains like ``gmail.com`` for these " +"assignments." +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "📑 Note" +msgstr "" + +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 +msgid "Notes are visible to all staff members, **including agents**." +msgstr "" + +#: ../manage/organizations/index.rst:126 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” " +"organization attributes?**" +msgstr "" + +#: ../manage/organizations/index.rst:129 +msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +msgstr "" + +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 +msgid "You can! To learn more, see :doc:`/system/objects`." +msgstr "" + +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 +msgid "▶️ Active" +msgstr "" + +#: ../manage/organizations/index.rst:134 +msgid "" +"Disabling this flag is a soft alternative to deleting an organization. So " +"what’s the difference?" +msgstr "" + +#: ../manage/organizations/index.rst:137 +msgid "" +"There is no way to restore a deleted organization; inactive organizations " +"can be reactivated at any time." +msgstr "" + +#: ../manage/organizations/index.rst:140 +msgid "Inactive organizations still appear in search results:" +msgstr "" + +#: ../manage/organizations/index.rst:0 +msgid "An inactive organization displayed in a quick search list" +msgstr "" + +#: ../manage/organizations/index.rst:146 +msgid "" +"A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +"inactive organizations are greyed out." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:2 +msgid "Managing organizations via CSV Import" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:4 +#: ../manage/users/via-csv-import.rst:4 +msgid "" +"If your organization has information about customers (or personnel) already " +"stored in a directory system that can export to CSV, you can batch-import " +"them into Zammad in just three steps." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "The CSV import dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:12 +#: ../manage/users/via-csv-import.rst:12 +msgid "Use the **Import** button to open the CSV import dialog." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:15 +#: ../manage/users/via-csv-import.rst:23 +msgid "Step 1: Inspect the sample .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:17 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your organization data." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:22 +msgid "Step 2: Export your organization data to .csv" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:24 +#: ../manage/users/via-csv-import.rst:32 +msgid "" +"Prepare your .csv file according to the format found in Step 1 above. Note " +"that:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:26 +#: ../manage/users/via-csv-import.rst:34 +msgid "the ``id`` attribute (column) should be left blank or removed entirely;" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:27 +msgid "the ``name`` attribute is **required**; and" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:28 +#: ../manage/users/via-csv-import.rst:36 +msgid "" +"any other columns may be safely omitted as long as each row has the same " +"number of fields (commas)." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:31 +#: ../manage/users/via-csv-import.rst:39 +msgid "For instance:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:46 +msgid "" +"Several organization members can be added: Ensure to provide the users email " +"address as shown above with empty values." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:50 +#: ../manage/users/via-csv-import.rst:48 +msgid "Step 3: Import your .csv to Zammad" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:52 +msgid "" +"Once your raw organization data has been submitted, Zammad will perform a " +"test run to compute the number of affected records:" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import test run and confirmation dialog" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:60 +#: ../manage/users/via-csv-import.rst:58 +msgid "CSV import always begins with a preview / test run." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:62 +#: ../manage/users/via-csv-import.rst:60 +msgid "🤔 **How does it know when to create new records and when to update?**" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:64 +msgid "" +"Records are updated when the imported data contains a ``name`` that matches " +"an existing organization entry." +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:67 +#: ../manage/users/via-csv-import.rst:65 +msgid "" +"Click **Yes, start real import** to proceed. (If you’re importing a lot of " +"records, be patient—it may take a minute.)" +msgstr "" + +#: ../manage/organizations/via-csv-import.rst:70 +#: ../manage/users/via-csv-import.rst:68 +msgid "That’s it! 🎉🎉🎉" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:2 +msgid "Managing organizations via the admin panel" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:4 +msgid "" +"The “Organizations” panel provides tools to manually manage organization " +"entries." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:18 +#: ../manage/users/via-the-admin-panel.rst:15 +msgid "👥 Creating and editing users" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "Screencast showing an organization being created." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:12 +msgid "" +"Click the **New Organization** button to open the New Organization dialog, " +"or click on an existing organization to edit." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:17 +msgid "" +"See :ref:`organization-details-reference` for help with the New/Edit " +"Organization dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:40 +msgid "🗑️ Deleting organizations" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:21 +msgid "" +"Organizations currently can only be removed via data privacy by deleting the " +"last organization member and then choose ``yes`` for *Delete organization?*." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing an organization being selected for deletion with\n" +"its last organizational member." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:30 +#: ../manage/users/via-the-admin-panel.rst:22 +msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:32 +#: ../manage/users/via-the-admin-panel.rst:24 +msgid "💥 **Deleting a customer destroys all their associated tickets!**" +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:34 +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "To learn more, see :doc:`/system/data-privacy`." +msgstr "" + +#: ../manage/organizations/via-the-admin-panel.rst:38 +msgid "" +"Technically organization removal is possible via `Zammad's API`_, however, " +"this only works in very specific situations. You may want to stick to data " +"privacy as of now." +msgstr "" + +#: ../manage/overviews.rst:2 ../manage/slas/index.rst:67 +msgid "Overviews" +msgstr "" + +#: ../manage/overviews.rst:4 +msgid "" +"You can provide overviews to your agents and customers. They can be used as " +"a kind of worklist of tasks that the agent is supposed to work off. You can " +"also create individual reports for individual agents or agent groups." +msgstr "" + +#: ../manage/overviews.rst:8 +msgid "" +"In the Overview Management Area you can add new overviews, edit or delete " +"them." +msgstr "" + +#: ../manage/overviews.rst:12 +msgid "" +"Please note that Overviews can cause performance issues leading to no longer " +"or less often refreshing overviews!" +msgstr "" + +#: ../manage/overviews.rst:15 +msgid "" +"Whenever possible, try to use the same overviews for as many agents and " +"groups as possible to keep the number of overviews low. For best results, " +"you might want to use between 15-20 overviews maximum. Also, any overview " +"will only show a total of 2100 elements." +msgstr "" + +#: ../manage/overviews.rst:22 +msgid "" +"Overviews will only show tickets to your users, that the user have rights on " +"(group or role based)." +msgstr "" + +#: ../manage/overviews.rst:25 +msgid "The following attributes can be set when creating an overview:" +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "" +"Available for the following roles / Restrict to only the following users" +msgstr "" + +#: ../manage/overviews.rst:33 +msgid "" +"Roles are assigned to users, per default there are agents, admins and " +"customers. Further information about :doc:`roles/index`." +msgstr "" + +#: ../manage/overviews.rst:36 +msgid "The setting \"available for the following roles\" is mandatory." +msgstr "" + +#: ../manage/overviews.rst:38 +msgid "Define roles that are supposed to see and use the overview in question." +msgstr "" + +#: ../manage/overviews.rst:40 +msgid "" +"If your overview is rather specific for a sub group of users of your role, " +"use the *\"Restrict to only the following users\"* option to further " +"restrict the visibility of the overview to defined users." +msgstr "" + +#: ../manage/overviews.rst:46 +msgid "You will still have to provide a role!" +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Only available for users with shared organization" +msgstr "" + +#: ../manage/overviews.rst:53 +msgid "" +"Shared organization is a setting in the organization management. See :doc:`/" +"manage/organizations/index` for more information." +msgstr "" + +#: ../manage/overviews.rst:56 +msgid "" +"This is only important if the available role is a customer. When deciding " +"whether yes or no is selected, it must be considered to what extent this " +"makes sense - for example, if a customer sees only his own tickets, many " +"views are usually not necessary..." +msgstr "" + +#: ../manage/overviews.rst:61 +msgid "Users also refers to the customer role in this case." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Available for users which are replacements for other users." +msgstr "" + +#: ../manage/overviews.rst:66 +msgid "" +"This selection refers to the setting in the user preferences (profile-pic in " +"the left corner --> profile -->) \"out of office\". If this option is " +"checked, this selection is only displayed if someone has been entered as a " +"substitution." +msgstr "" + +#: ../manage/overviews.rst:71 +msgid "" +"**For example:** Agent A is on vacation and Agent B will take care of his " +"tickets. Then an overview can be set up, which only shows Agent B all new " +"tickets from Agent A for this period of time, without having to search for " +"them separately." +msgstr "" + +#: ../manage/overviews.rst:78 +msgid "Replacement users are part of our `Out of Office function`_." +msgstr "" + +#: ../manage/overviews.rst:91 +msgid "Conditions for shown tickets" +msgstr "" + +#: ../manage/overviews.rst:86 +msgid "" +"What conditions should the listed tickets contain? (it is like a filter) You " +"can add more than one condition. In the preview you have the possibility to " +"double check if your entry of the conditions makes sense by directly " +"displaying tickets that match your filtering." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:1 +msgid "**👋 Looking for more depth explanation on conditions? 🤓**" +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:3 +msgid "" +"Many condition settings in Zammad, no matter if in ticket scope or not, re-" +"appear in several places of Zammad. For this reason we created a dedicated " +"documentation section to reduce duplicate drag." +msgstr "" + +#: ../misc/object-conditions/conditioning-depth-hint.include.rst:7 +msgid "" +"Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉" +msgstr "" + +#: ../manage/overviews.rst:111 ../system/core-workflows/learn-by-example.rst:24 +msgid "Attributes" +msgstr "" + +#: ../manage/overviews.rst:96 +msgid "Which attributes shall be shown in the overview? (column headers)" +msgstr "" + +#: ../manage/overviews.rst:98 +msgid "" +"With this setting you can select the headlines of your overview. Depending " +"on which information is important in this selection, it can be displayed " +"individually. For this example \"Unassigned and open\" the overview would " +"look like this:" +msgstr "" + +#: ../manage/overviews.rst:105 +msgid "" +"These settings can also be adjusted individually by admins at a later time " +"(In the overview, top right: Options)." +msgstr "" + +#: ../manage/overviews.rst:110 +msgid "" +"Please note that overview column and sort settings are global settings which " +"affect all users seeing those overviews." +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "Sorting, Grouping and Active" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting by" +msgstr "" + +#: ../manage/overviews.rst:117 +msgid "" +"In which order should the tickets be displayed? (Sorted by the attributes)" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Sorting order" +msgstr "" + +#: ../manage/overviews.rst:120 +msgid "The direction of the sorting." +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping by" +msgstr "" + +#: ../manage/overviews.rst:123 +msgid "Should the tickets be grouped by a specific attribute within the list?" +msgstr "" + +#: ../manage/overviews.rst:0 +msgid "Grouping order" +msgstr "" + +#: ../manage/overviews.rst:126 +msgid "The direction of the grouping." +msgstr "" + +#: ../manage/overviews.rst:129 +msgid "" +"Should the overview be active or not? Rather than deleting an overview " +"entirely, you can set it to inactive to make it unavailable to your users." +msgstr "" + +#: ../manage/overviews.rst:135 +msgid "" +"Users can define their own overview order. Renaming or reordering overviews " +"has no effect on custom orders!" +msgstr "" + +#: ../manage/overviews.rst:138 +msgid "You can learn more about this setting in the `user documentation`_." +msgstr "" + +#: ../manage/public-links.rst:2 +msgid "Public Links" +msgstr "" + +#: ../manage/public-links.rst:4 +msgid "" +"Public links allow you to provide important links at different places within " +"the UI of Zammad. This allows you not just to provide legal information like " +"e.g. data privacy or contact information. You can also provide further " +"useful links to other services if needed." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "" +"Screenshot showing the public links management interface within\n" +"the settings" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid "Learn how to ..." +msgstr "" + +#: ../manage/public-links.rst:14 +msgid ":ref:`public_links_add_new`" +msgstr "" + +#: ../manage/public-links.rst:15 +msgid ":ref:`public_links_manage_existing`" +msgstr "" + +#: ../manage/public-links.rst:17 +msgid ":ref:`public_links_rearrange`" +msgstr "" + +#: ../manage/public-links.rst:18 +msgid ":ref:`public_links_actions` (Cloning & Removing)" +msgstr "" + +#: ../manage/public-links.rst:25 +msgid "Adding new public links" +msgstr "" + +#: ../manage/public-links.rst:27 +msgid "" +"You can add new public links via the *New Public Link* button on the upper " +"right. You'll see a new dialogue that consists of the following information." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "Link" +msgstr "" + +#: ../manage/public-links.rst:31 +msgid "This is the actual target page you're linking to." +msgstr "" + +#: ../manage/public-links.rst:35 +msgid "" +"Zammad only allows URLs that start with either ``http://`` or ``https://``." +msgstr "" + +#: ../manage/public-links.rst:40 +msgid "" +"You may not use data privacy and terms of service URLs of ``zammad.com`` nor " +"``zammad.org``." +msgstr "" + +#: ../manage/public-links.rst:47 +msgid "Why?" +msgstr "" + +#: ../manage/public-links.rst:44 +msgid "" +"Every instance is special on its own. Every hosting is different, data " +"retention and other things do not fit as every company using Zammad handles " +"these matters differently." +msgstr "" + +#: ../manage/public-links.rst:48 +msgid "This function was made to allow you to link to your *own resources*." +msgstr "" + +#: ../manage/public-links.rst:51 +msgid "" +"This is the regular text your user sees as the link text. You may want to " +"keep the title as short as possible as it's displayed in the footer of the " +"context you'll later select." +msgstr "" + +#: ../manage/public-links.rst:56 +msgid "" +"The description for URLs is an accessibility feature that helps users with " +"screen readers to better understand the scope of the URL. It will also be " +"shown by normal browsers when hovering over the link in question." +msgstr "" + +#: ../manage/public-links.rst:60 +msgid "Use this to describe the link. This value is *optional*." +msgstr "" + +#: ../manage/public-links.rst:103 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Context" +msgstr "" + +#: ../manage/public-links.rst:64 +msgid "" +"The context setting allows you to choose one or several places where this " +"link should be displayed. Depending on your choice, Zammad will then show " +"the links on the relevant pages." +msgstr "" + +#: ../manage/public-links.rst:68 +msgid "You can currently select from:" +msgstr "" + +#: ../manage/public-links.rst:70 ../manage/public-links.rst:85 +msgid "Forgot Password Screen" +msgstr "" + +#: ../manage/public-links.rst:74 +msgid "" +"This context *does not* affect the :ref:`security_password_login` function." +msgstr "" + +#: ../manage/public-links.rst:77 ../manage/public-links.rst:92 +msgid "Login Screen" +msgstr "" + +#: ../manage/public-links.rst:78 ../manage/public-links.rst:99 +msgid "Signup Screen" +msgstr "" + +#: ../manage/public-links.rst:80 +msgid "" +"To help you understand scopes better, here's the different scopes as a " +"screenshot. Note that we intentionally did set all links for all contexts. 🤓" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's forgot password page with custom\n" +"public links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "" +"Screenshot showing Zammad's login page with custom public\n" +"links" +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screenshot showing Zammad's signup page with custom public links" +msgstr "" + +#: ../manage/public-links.rst:110 +msgid "Display in new tab" +msgstr "" + +#: ../manage/public-links.rst:106 +msgid "" +"This setting allows you to determine if Zammad should tell the browser to " +"either open the URL in a new tab or within the existing tab." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Opening URLs in the same tab may cause inconvenience to the user." +msgstr "" + +#: ../manage/public-links.rst:115 +msgid "Manage existing public links" +msgstr "" + +#: ../manage/public-links.rst:120 +msgid "Re-arrange links" +msgstr "" + +#: ../manage/public-links.rst:122 +msgid "" +"By default Zammad sorts your public links in the order you've created them. " +"That may be a problem if you add a link later on. For this reason you can " +"easily change the link order by dragging them to another position." +msgstr "" + +#: ../manage/public-links.rst:126 +msgid "These changes are affective immediately." +msgstr "" + +#: ../manage/public-links.rst:None +msgid "Screencast showing re-arranging public links by using drag & drop" +msgstr "" + +#: ../manage/public-links.rst:134 +msgid "Actions for existing links" +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "Updating existing entries" +msgstr "" + +#: ../manage/public-links.rst:137 +msgid "" +"Got a typo in your URL or title? Want to change the context the link is " +"being shown on? No problem! Just click on the affected link title and adjust " +"the entry as needed." +msgstr "" + +#: ../manage/public-links.rst:141 +msgid "You'll be given the same options as you have during the link creation." +msgstr "" + +#: ../manage/public-links.rst:151 +msgid "Cloning" +msgstr "" + +#: ../manage/public-links.rst:144 +msgid "" +"If you want to add a new link that's very similar to an existing one, simply " +"click on ⋮ and select *Clone*." +msgstr "" + +#: ../manage/public-links.rst:147 +msgid "" +"Zammad will open a new public link dialogue with the existing settings " +"filled in." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link cloning via ⋮ Actions → Clone" +msgstr "" + +#: ../manage/public-links.rst:162 +msgid "Removing" +msgstr "" + +#: ../manage/public-links.rst:154 +msgid "" +"If you no longer require a public link, you can remove it by using ⋮ and " +"selecting *Delete*. Zammad will ensure that you really want to remove the " +"entry with a modal." +msgstr "" + +#: ../manage/public-links.rst:160 +msgid "" +"Deleting is **final**. There's no way to bring back removed public links." +msgstr "" + +#: ../manage/public-links.rst:0 +msgid "Screencast showing the public link removal via ⋮ Actions → Delete" +msgstr "" + +#: ../manage/report-profiles.rst:2 +msgid "Report Profiles" +msgstr "" + +#: ../manage/report-profiles.rst:4 +msgid "" +"Report profiles are used to restrict / filter report-results. The idea of " +"the profiles is to limit the number of tickets and determine the type of " +"tickets you want to analyze. You can create any number of profiles in the " +"Admin Interface in the \"Report Profile\" area. The edit-mask looks like " +"this:" +msgstr "" + +#: ../manage/report-profiles.rst:11 +msgid "" +"This example shows the statistics of all tickets of the organization " +"\"Awesome Customer\" that were created in the last month." +msgstr "" + +#: ../manage/report-profiles.rst:14 +msgid "" +"The filters can be combined with each other as desired. The filters build on " +"each other, which means that they are further restricted per additional " +"attribute." +msgstr "" + +#: ../manage/report-profiles.rst:18 +msgid "" +"All configured filters are displayed in the statistics area and you can " +"switch between them with one click:" +msgstr "" + +#: ../manage/report-profiles.rst:25 +msgid "Further information about the reporting:" +msgstr "" + +#: ../manage/report-profiles.rst:27 +msgid "" +"The time period and time interval can be changed with one click (the graphic " +"adapts itself directly):" +msgstr "" + +#: ../manage/report-profiles.rst:32 +msgid "" +"You can filter the Create Channels (Phone, email, Twitter,...) and " +"Communication (Phone, email, Twitter,...) and select metrics (choose from " +"the menu bar in the upper left corner - currently Ticket Count, Create " +"Channels, Communication). Here are all tickets with a certain metric of a " +"profile evaluated." +msgstr "" + +#: ../manage/report-profiles.rst:39 +msgid "" +"The list below the graphic shows the tickets that have been filtered out. " +"This can be downloaded as CSV and processed in a statistics program:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:2 +msgid "Admin Permissions" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:6 ../manage/roles/index.rst:105 +#: ../manage/roles/user-preferences-permissions.rst:6 +msgid "" +"📁 **Permissions are namespaced**, which is sort of like having files inside " +"of folders." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``admin`` namespace. " +"You can select them individually, or you can just select ``admin`` to enable " +"the whole bunch." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Admin permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:20 +msgid "Admin permissions are shown at the top of the New Role dialog..." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "Screenshot showing admin settings within Zammad." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:29 +msgid "...and give users access to the pages of the Admin Panel." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:33 +#: ../manage/roles/agent-permissions.rst:29 +#: ../manage/roles/user-preferences-permissions.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:110 +msgid "``admin.api``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:36 +msgid "`System > API `_" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:111 +msgid "``admin.branding``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:39 +msgid ":doc:`Settings > Branding `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:112 +msgid "``admin.calendar``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:42 +msgid "" +":doc:`Manage > Calendars ` (required for :doc:`/manage/" +"slas/index`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:113 +msgid "``admin.channel_chat``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:46 +msgid ":doc:`Channels > Chat `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:48 +msgid "🤓 **Trying to grant access to send messages in live chats?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:50 +msgid "Use ``chat.agent`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:114 +msgid "``admin.channel_email``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:53 +msgid ":doc:`Channels > Email `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_facebook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:56 +msgid ":doc:`Channels > Facebook `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:58 +msgid "🤓 **Trying to grant access to view/update tickets from Facebook?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:60 +msgid "That's in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_formular``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:63 +msgid ":doc:`Channels > Form `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_google``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:66 +msgid ":doc:`Channels > Google `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_microsoft365``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:69 +msgid ":doc:`Channels > Microsoft 365 `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_sms``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:72 +msgid "Channels > SMS" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_telegram``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:75 +msgid ":doc:`Channels > Telegram `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:77 +msgid "🤓 **Trying to grant access to view/update tickets from Telegram?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:79 +#: ../manage/roles/admin-permissions.rst:86 +msgid "That’s in :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_twitter``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:82 +msgid ":doc:`Channels > Twitter `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid "🤓 **Trying to grant access to view/update tickets from Twitter?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.channel_web``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:89 +msgid ":doc:`Channels > Web `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.core_workflows``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:92 +msgid ":doc:`System > Core Workflows `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.data_privacy``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:95 +msgid ":doc:`System > Data Privacy `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:99 +msgid "" +"🔥 This permission allows users to permanently delete data on the system. " +"Proceed with caution!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.group``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:103 +msgid ":doc:`Manage > Groups `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.integration``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:106 +msgid ":doc:`System > Integrations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.knowledge_base``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:109 +msgid ":doc:`Manage > Knowledge Base `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:111 +msgid "🤓 **Trying to grant access to read/edit knowledge base articles?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:113 +msgid "" +"Use ``knowledge_base.reader`` and ``knowledge_base.editor`` instead, and " +"double-check the answer's `visibility`_." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.macro``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:120 +msgid ":doc:`Manage > Macros `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:122 +msgid "In some cases, macros may also require ``admin.tag``." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.maintenance``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`System > Maintenance `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.monitoring``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:128 +msgid ":doc:`System > Monitoring `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.object``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:131 +msgid ":doc:`System > Objects `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.organization``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:134 +msgid ":doc:`Manage > Organizations `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:136 +msgid "" +"Agents can access existing organizations from the search bar, even without " +"this permission. They can even edit an organization’s name, domain, and " +"notes!" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.overview``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:141 +msgid ":doc:`Manage > Overviews`" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.package``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:144 +msgid ":doc:`System > Packages `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.report_profile``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:147 +msgid ":doc:`Manage > Report Profiles `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:149 +msgid "🤓 **Trying to grant access to view reports?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:151 +msgid "Use ``report`` instead." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.role``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:154 +msgid ":doc:`Manage > Roles `. 🧐" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.scheduler``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:157 +msgid ":doc:`Manage > Scheduler ` for automation on tickets" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.security``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:160 +msgid "" +":doc:`Settings > Security ` settings of Zammad This also " +"covers third party authentications." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.session``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:164 +msgid ":doc:`System > Sessions `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.setting_system``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":doc:`Settings > System ` of Zammad" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.sla``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":doc:`Manage > SLAs `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.tag``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":doc:`Manage > Tags `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.template``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":doc:`Manage > Templates `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.text_module``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:179 +msgid ":doc:`Manage > Text Modules `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.ticket``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:182 +msgid "" +":doc:`Settings > Tickets ` (does not grant access to :doc:" +"`/misc/composer`)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.time_accounting``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:186 +msgid ":doc:`Manage > Time Accounting `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:190 +msgid "" +"This permission may be useful for accounting personnel if they need to be " +"able to export timekeeping records." +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.translation``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid "" +":doc:`System > Translations ` (also enables inline " +"translation)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 +msgid "``admin.trigger``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:198 +msgid ":doc:`Manage > Triggers `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``admin.user``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:201 +msgid ":doc:`Manage > Users `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:203 +msgid "🤔 **I thought agents could already manage user accounts?**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:205 +msgid "Agents can create and edit **customers**, but they can’t:" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:207 +msgid "modify anyone's permissions (roles or groups)" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:208 +msgid "modify anyone's passwords" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:209 +msgid "edit other agent's accounts" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:211 +msgid "🏴‍☠️ **This permission allows users to hijack other user sessions.**" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:213 +msgid "" +"To learn more, see :ref:`Taking over a user's session `." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:2 +msgid "Agent Permissions" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:6 +msgid "" +"The permissions listed on this page grant access to features that have to be " +"enabled or configured system-wide in the Admin Panel first." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Agent permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:16 +msgid "Agent permissions are shown in the middle of the New Role dialog..." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:24 +msgid "" +"...and give users access to new sidebar tabs for communicating with " +"customers." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``chat.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:32 +msgid "`💬 Customer Chat`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:34 +msgid "🤓 Requires configuration of :doc:`Chat Channel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``cti.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:40 +msgid "Provides access to `📞 Caller Log`_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:42 +msgid "🤓 Requires configuration of either integrations" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:44 +msgid ":doc:`Generic CTI `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:45 +msgid ":doc:`placetel `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:46 +msgid ":doc:`sipgate `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "knowledge_base" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:52 +msgid "" +"`📕 Knowledge Base `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +msgid "``knowledge_base.editor``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:55 +msgid "create/edit privileges" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:57 +msgid "Editor permissions always include reader permissions." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``knowledge_base.reader``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:60 +msgid "read privileges for internal content" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:64 +msgid "Public articles are always visible." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:68 +msgid "Zammad supports `granular permissions on knowledge base categories`_." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:70 +msgid "" +"This function allows *agents with editor* permissions to restrict specific " +"internal categories & answers to chosen roles." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:73 +msgid "" +"In order to allow your agents to set granular role permissions, the roles in " +"question require at least reader permission for the knowledge base." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:79 +msgid "" +"Keep in mind that this may be dangerous, as reader permission provides " +"access to internal answers!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 +msgid "``report``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:86 +msgid ":doc:`📈 Reporting `" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:88 +msgid "🙅 **Never grant this permission to your customers.**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:90 +msgid "" +"Giving customers access to reporting constitutes a serious data breach, as " +"it includes **all ticket and user information across the entire system**!" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:93 +msgid "This permission is the exception to the rule on this page:" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:95 +msgid "the feature it enables is not for communicating with customers;" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:96 +msgid "the button appears at the *bottom* of the sidebar; and" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:97 +msgid "it is typically reserved for admins and supervisors." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:0 ../manage/roles/index.rst:0 +#: ../settings/security/base.rst:102 +msgid "``ticket.agent``" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:101 +msgid "" +"`🗒️ (Agent) Overviews `_" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:105 +msgid "🤔 **What’s this big table doing here in the middle of my permissions?**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:111 +msgid "" +"The group access table is shown when there is **more than one active group** " +"in the system." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:114 +msgid "" +"Okay, so remember when we said that :ref:`“roles are just collections of " +"permissions” `? That wasn't *entirely* true—they can also be " +"collections of **group access levels**." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:119 +msgid "To learn more, see :doc:`/manage/groups/access-levels`." +msgstr "" + +#: ../manage/roles/agent-permissions.rst:121 +msgid "🤓 **Point of technicality**" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:123 +msgid "" +"You can assign both agent and customer roles to the same user — but you " +"**can't** assign both ``ticket.agent`` and ``ticket.customer`` *permissions* " +"to the same *role!*" +msgstr "" + +#: ../manage/roles/agent-permissions.rst:127 +msgid "" +"To make it work, you need two separate roles: one with ``ticket.agent`` and " +"the other with ``ticket.customer``." +msgstr "" + +#: ../manage/roles/index.rst:2 +msgid "Roles" +msgstr "" + +#: ../manage/roles/index.rst:4 +msgid "" +"If you’re already using Zammad, you’ll know that users can be **admins**, " +"**agents**, or **customers**. These are Zammad’s built-in roles, and they’re " +"the tip of the iceberg of its powerful, flexible, and fine-grained " +"permission system." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Role overview within Zammad's admin settings." +msgstr "" + +#: ../manage/roles/index.rst:14 +msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." +msgstr "" + +#: ../manage/roles/index.rst:16 +msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgstr "" + +#: ../manage/roles/index.rst:18 +msgid "" +"Why would you want this? Agents get :doc:`overviews ` of " +"all the tickets they’re *assigned to* (among other things), while customers " +"get an overview of all the tickets they’ve *opened*. But some teams use " +"Zammad for both internal and public communication, so their agents need both." +msgstr "" + +#: ../manage/roles/index.rst:25 +msgid "" +"Having both roles also changes what you see in the ticket view, depending on " +"whether you’re the “customer” or not." +msgstr "" + +#: ../manage/roles/index.rst:28 +msgid "💡 **LDAP/Active Directory users:**" +msgstr "" + +#: ../manage/roles/index.rst:30 +msgid "" +"Syncing your LDAP “groups” to Zammad roles can make access management *way* " +"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgstr "" + +#: ../manage/roles/index.rst:37 +msgid "What Is a Role?" +msgstr "" + +#: ../manage/roles/index.rst:39 +msgid "" +"**tl;dr** Some users can do things others can’t (like close a ticket). Users " +"have roles, roles have permissions, and permissions are what make those " +"actions possible." +msgstr "" + +#: ../manage/roles/index.rst:43 +msgid "So what exactly are permissions, then?" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "List of permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/index.rst:50 +msgid "" +"The ``admin.calendar`` permission gives you access to the **Manage > " +"Calendars** admin panel." +msgstr "" + +#: ../manage/roles/index.rst:53 +msgid "" +"Simply put, permissions are names for all the different things users might " +"want to do throughout the system, such as:" +msgstr "" + +#: ../manage/roles/index.rst:56 +msgid "respond to live chat messages" +msgstr "" + +#: ../manage/roles/index.rst:57 +msgid "update tickets" +msgstr "" + +#: ../manage/roles/index.rst:58 +msgid "access the **Manage > Users** admin panel" +msgstr "" + +#: ../manage/roles/index.rst:59 +msgid "create/edit knowledge base articles" +msgstr "" + +#: ../manage/roles/index.rst:61 +msgid "" +"Zammad has dozens of these permissions, which is a lot to keep track of. So " +"instead of saying “This user has permissions A, B, and C”, Zammad says “The " +"*agent role* has permissions A, B, and C, and this user is an agent.”" +msgstr "" + +#: ../manage/roles/index.rst:67 +msgid "" +"This makes creating user accounts for new agents a whole lot simpler, and it " +"also makes it easier to invent a new permission D and say “All existing " +"agents can do *that* now, too.”" +msgstr "" + +#: ../manage/roles/index.rst:71 +msgid "" +"In short, roles are just collections of permissions that you can give to a " +"user. The built-in admin, agent, and customer roles are enough for many " +"teams, but Zammad gives you the freedom to custom-build your own." +msgstr "" + +#: ../manage/roles/index.rst:75 +msgid "And to do that, you’ll need to know what each permission does." +msgstr "" + +#: ../manage/roles/index.rst:80 +msgid "Reference Guide: Permissions" +msgstr "" + +#: ../manage/roles/index.rst:89 +msgid "Broadly speaking, there are four types of permissions:" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid ":doc:`🛡️ Admin `" +msgstr "" + +#: ../manage/roles/index.rst:92 +msgid "for access to each page of the Admin Panel" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid ":doc:`🕵️ Agent `" +msgstr "" + +#: ../manage/roles/index.rst:95 +msgid "for access to customer communications" +msgstr "" + +#: ../manage/roles/index.rst:100 +msgid "👤 Customer" +msgstr "" + +#: ../manage/roles/index.rst:98 +msgid "" +"Without the ``ticket.customer`` permission, customers can’t see the **My " +"Ticket** overview—but they can still log in and open new tickets!" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid ":doc:`🎛️ User Preferences `" +msgstr "" + +#: ../manage/roles/index.rst:103 +msgid "" +"for access to your own `user profile `_" +msgstr "" + +#: ../manage/roles/index.rst:108 +msgid "These permissions:" +msgstr "" + +#: ../manage/roles/index.rst:115 +msgid "...and 30+ more" +msgstr "" + +#: ../manage/roles/index.rst:117 +msgid "" +"all belong to the ``admin`` namespace. You can select them individually, or " +"you can just select ``admin`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/index.rst:122 +msgid "Role Details" +msgstr "" + +#: ../manage/roles/index.rst:135 +msgid "Default at signup" +msgstr "" + +#: ../manage/roles/index.rst:125 +msgid "" +"Every new user must be assigned at least one role upon creation. This " +"attribute decides which role to give new users by default (which usually " +"happens when creating a new ticket for a new customer)." +msgstr "" + +#: ../manage/roles/index.rst:0 +msgid "Role overview in the admin panel, showing default role" +msgstr "" + +#: ../manage/roles/index.rst:133 +msgid "" +"The default role is identified in the overview of the **Manage > Roles** " +"admin panel." +msgstr "" + +#: ../manage/roles/index.rst:136 +msgid "🙅 **Default roles should never provide admin/agent permissions.**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:2 +msgid "User Preferences Permissions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:9 +msgid "" +"The permissions listed on this page all belong to the ``user_preferences`` " +"namespace. You can select them individually, or you can just select " +"``user_preferences`` to enable the whole bunch." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User preferences permissions in the New Role dialog" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:21 +msgid "" +"User preferences permissions are shown at the bottom of the New Role " +"dialog..." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "User profile page" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:31 +msgid "...and give users access to the pages of their `User Profile`_." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.access_token``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:41 +msgid "Generate API tokens to control Zammad via the `REST API`_" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:43 +#: ../manage/roles/user-preferences-permissions.rst:60 +#: ../manage/roles/user-preferences-permissions.rst:92 +msgid "💡 **Security Tip**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:45 +msgid "" +"Generated tokens will never have more permissions than the user that " +"generated them." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.avatar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:52 +msgid "Override the default Gravatar with a custom avatar" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.calendar``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:55 +msgid "Configure the calendar feed" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.device``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:58 +msgid "Manage device login sessions" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:62 +msgid "" +"Revoking this permission disables “Login detected from a new location” " +"notification emails." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:65 +msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.language``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:68 +msgid "Configure the UI locale/language" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.linked_accounts``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:71 +msgid "" +"Manually link accounts after signing in with :doc:`third-party " +"authentication `" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:76 +msgid "" +"If :ref:`automatic account linking ` fails, this " +"is the only way your users can utilize third-party logins." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.notifications``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:80 +msgid "Configure ticket notification settings" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:84 +msgid "" +"Agents only receive ticket notifications for :doc:`groups they have “full” " +"access to `." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:87 +msgid "Customers can't receive ticket notifications at all." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.out_of_office``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:90 +msgid "Designate a substitute for out-of-office hours" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:94 +msgid "" +"Designating a substitute does **not** grant that person the permissions / :" +"doc:`group access levels ` of the agent " +"they're replacing." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.overview_sorting``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:98 +msgid "Allow your users to define their own overview order." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:102 +msgid "" +"The order your user chooses here cannot be overwritten by admins. Renaming " +"or resorting overviews has no effect on custom orders." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:107 +msgid "" +"This is an optional permission for customers and thus disabled by default." +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "``user_preferences.password``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:110 +msgid "Change account password" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:112 +msgid "🔑 **Third-party authentication / LDAP users:**" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:114 +msgid "" +"Be sure to **revoke this permission** for all your users. When using a third-" +"party identity server (like LDAP), the whole point is to let *it* take care " +"of authentication so that passwords never have to live in Zammad's database." +msgstr "" + +#: ../manage/scheduler.rst:2 +msgid "Scheduler" +msgstr "" + +#: ../manage/scheduler.rst:4 +msgid "" +"The scheduler performs time-based automated actions. You can set up your own " +"schedulers, configure at which points in time they should run, set up " +"conditions to determine which tickets they should affect, and then configure " +"the actions that you want to be executed on these tickets." +msgstr "" + +#: ../manage/scheduler.rst:11 +msgid "" +"Schedulers with *Action: Delete* are currently the only way in the Zammad " +"front end to permanently delete tickets. This limitation is intentional as " +"Zammad is designed to be revision-proof. A possible use case for such a " +"scheduler is to delete spam tickets some time after creation (e.g. 30 days)." +msgstr "" + +#: ../manage/scheduler.rst:18 +msgid "" +"While it is possible to delegate scheduler permissions to normal agents with " +"the ``admin/scheduler`` permission, it is inadvisable to do so. Malicious " +"agents could use a scheduler to access tickets in restricted groups (by " +"moving them to a non-restricted group) or to delete arbitrary tickets." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"variables` to build highly-customized email templates." +msgstr "" + +#: ../manage/scheduler.rst:0 +msgid "" +"Schedulers only perform ``2000`` tickets per run. This is a security " +"function in case you accidentally miss configure the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:32 +msgid "Add a new scheduler" +msgstr "" + +#: ../manage/scheduler.rst:37 +msgid "Choose a name for the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:46 +msgid "When should the job run?" +msgstr "" + +#: ../manage/scheduler.rst:40 +msgid "" +"Choose the points in time using :doc:`Zammad's timezone ` when the scheduler should run." +msgstr "" + +#: ../manage/scheduler.rst:45 +msgid "" +"The scheduler tasks are not saving any timezone information. Thus: Scheduler " +"tasks created prior Zammad 5.1 don't require any change." +msgstr "" + +#: ../manage/scheduler.rst:52 +msgid "Conditions for affected objects" +msgstr "" + +#: ../manage/scheduler.rst:49 +msgid "" +"Determine the ticket attributes (conditions) to limit on which tickets the " +"actions configured in step 5 are to be performed." +msgstr "" + +#: ../manage/scheduler.rst:55 +msgid "" +"This list previews some tickets that your conditions are matching and shows " +"a total of how many tickets are being matched. Use this to double-check the " +"entered conditions." +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Execute changes on objects" +msgstr "" + +#: ../manage/scheduler.rst:60 +msgid "Determine the changes to be made to the ticket." +msgstr "" + +#: ../manage/scheduler.rst:64 +msgid "Disable notifications" +msgstr "" + +#: ../manage/scheduler.rst:63 +msgid "" +"By default, actions triggered by schedulers won't send notifications. You " +"can override this here by setting this to *no*." +msgstr "" + +#: ../manage/scheduler.rst:67 +msgid "" +"You can use the note field to describe the purpose of the scheduler. This is " +"only visible to other admins when they are editing the scheduler. It is " +"*not* a way to add notes to tickets." +msgstr "" + +#: ../manage/scheduler.rst:72 +msgid "With this setting you can enable/disable the scheduler." +msgstr "" + +#: ../manage/scheduler.rst:74 +msgid "The scheduler shown in the screenshot would have the following effects:" +msgstr "" + +#: ../manage/scheduler.rst:76 +msgid "" +"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all " +"tickets which:" +msgstr "" + +#: ../manage/scheduler.rst:79 +msgid "are not closed or merged, and" +msgstr "" + +#: ../manage/scheduler.rst:80 +msgid "are assigned to the Sales group, and" +msgstr "" + +#: ../manage/scheduler.rst:81 +msgid "whose escalation was 30 minutes ago" +msgstr "" + +#: ../manage/scheduler.rst:83 +msgid "will be:" +msgstr "" + +#: ../manage/scheduler.rst:85 +msgid "assigned to Emma, and" +msgstr "" + +#: ../manage/scheduler.rst:86 +msgid "have their priority changed to 3 high." +msgstr "" + +#: ../manage/scheduler.rst:88 +msgid "" +"As a supervisor in the Sales group, this enables Emma to intercept and " +"process escalated tickets." +msgstr "" + +#: ../manage/scheduler.rst:91 +msgid "" +"Emma will not receive notifications when the scheduler assigns her these " +"tickets, and no note will be added to them." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:4 +msgid "" +"You can define several independent SLAs, however, ensure to have no " +"overlapping SLAs as their calculations may not work as you intended them " +"originally." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:None +msgid "Part of the configuration dialogue for SLAs" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:14 +msgid "" +"Updating existing SLA configurations *may* cause temporary performance " +"issues depending on your instance size and affected tickets. You may want to " +"perform those changes outside of your business hours." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:20 +msgid "" +"Communication type articles are not enough for your SLA? You can also " +"configure Zammad to allow **public** notes as fulfillment for SLA " +"requirements, `our console documentation`_ tells you how." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:28 +msgid "Give your SLA a meaningful name to quickly see what or who is affected." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:33 +msgid "Ticket selector" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:31 +msgid "Specify the conditions on which tickets this SLA should apply to." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:36 +msgid "" +"In the preview you see the selection of the tickets and double check whether " +"those are correct." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:44 +msgid "Calendar" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:40 +msgid "" +"Zammad calculates ticket escalations based on your business hours. It makes " +"no sense to escalate tickets when you're not in." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:43 +msgid "" +"Choose the correct calendar here. If you haven't set your business hours " +"yet, see :doc:`/manage/calendars` to learn more." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:101 +msgid "SLA Times" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:47 +msgid "" +"Define the escalation timings based on your working hours. Keep in mind that " +"if you defined 8 hour business hours per day, a 16 hour escalation will take " +"two business days." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:59 +msgid "First Response" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:52 +msgid "" +"Time frame for the first response (external call, email). This time is " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:57 +msgid "" +"The start time *does not* reset if you're e.g. moving the ticket into new " +"groups or different SLA calculations. That is because the creation time of " +"the ticket does not change - keep this in mind." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "Update Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:62 +msgid "" +"Time frame for every following response (external call, email). This time " +"either counts from ticket creation (if no first response is set) or *after* " +"the first response was done." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "between agent updates" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:67 +msgid "" +"In this scenario your agent have to respond every ``n`` hours depending on " +"your configuration. This causes Zammad to not care if your customer replied " +"or not." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:73 +msgid "This setting can be quiet stressful for your agents." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:77 +msgid "for an agent to respond" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:76 +msgid "" +"From the moment your customer replied to the ticket, your agents have the " +"configured time amount to respond until the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:86 +msgid "Solution Time" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:80 +msgid "" +"Time frame for solving the problem (setting the ticket to a closed state " +"type)." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:85 +msgid "" +"This escalation timing *does not* care about ticket responses. It's being " +"calculated from the ticket creation." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:88 +msgid "" +"It is up to you if you set one, two or all three times. When the SLA time is " +"reached, the ticket escalates." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:93 +msgid "" +"*First response* and *Solution time* can only apply once. Update time " +"applies until the ticket has been solved or the SLA no longer matches your " +"criteria." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:97 +msgid "" +"The only way to stop escalations in default installations is to set the " +"ticket to either a pending reminder or pending close. **However**: as soon " +"as the ticket is being set to open (e.g. by a customer responding) the " +"ticket may instantly escalate depending on its age and your configuration." +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:105 +msgid "" +"Ticket escalations will notify all affected agents. This highly depends on " +"their chosen notification settings (Profile). Escalated tickets can also be " +"filtered for:" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:109 +msgid "by searching" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:110 +#: ../misc/object-conditions/index.rst:15 +msgid ":doc:`/manage/trigger`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:111 +#: ../misc/object-conditions/index.rst:16 +msgid ":doc:`/manage/scheduler`" +msgstr "" + +#: ../manage/slas/how-do-they-work.rst:112 +#: ../misc/object-conditions/index.rst:13 +msgid ":doc:`/manage/overviews`" +msgstr "" + +#: ../manage/slas/index.rst:2 +msgid "SLAs" +msgstr "" + +#: ../manage/slas/index.rst:4 +msgid "" +"Service Level Agreements, abbreviated SLAs, help you to meet specific " +"response times for your customers' requests. This way you can define goals " +"such as answering every inquiry within eight hours. If you are at risk of " +"missing this target, Zammad will alert you." +msgstr "" + +#: ../manage/slas/index.rst:None +msgid "Screenshot showing SLA management with configured SLA levels" +msgstr "" + +#: ../manage/slas/index.rst:14 +msgid "" +"Agents will be notified via several, optional ways. You can provide " +"overviews for escalated or soon to escalate tickets to help you agents. " +"Also, agents can check the current applying SLA timings of tickets at any " +"time." +msgstr "" + +#: ../manage/slas/index.rst:26 +msgid "Online notifications" +msgstr "" + +#: ../manage/slas/index.rst:19 ../manage/slas/index.rst:29 +msgid "" +"Zammad will warn agents roughly 15 minute before escalation and when the " +"ticket finally escalates. This depends on the notification configuration of " +"your agent." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing two notifications: One upcoming escalation and\n" +"one escalated ticket" +msgstr "" + +#: ../manage/slas/index.rst:51 +msgid "Email notifications" +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that's going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:39 +msgid "Notification by mail that a ticket is going to escalate." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Email notification for a ticket that escalated." +msgstr "" + +#: ../manage/slas/index.rst:47 +msgid "Notification by mail that a ticket has escalated." +msgstr "" + +#: ../manage/slas/index.rst:51 ../manage/slas/index.rst:92 +#: ../misc/object-conditions/basics.rst:80 +#: ../misc/object-conditions/basics.rst:96 +#: ../misc/object-conditions/basics.rst:124 +#: ../misc/object-conditions/basics.rst:152 +#: ../misc/object-conditions/basics.rst:166 +#: ../misc/object-conditions/basics.rst:189 +#: ../misc/object-conditions/basics.rst:214 +#: ../misc/object-conditions/basics.rst:240 +#: ../misc/object-conditions/basics.rst:264 +#: ../misc/object-conditions/basics.rst:285 +#: ../misc/object-conditions/basics.rst:303 +#: ../misc/object-conditions/basics.rst:317 +#: ../misc/object-conditions/basics.rst:336 +#: ../misc/object-conditions/basics.rst:422 +#: ../misc/object-conditions/basics.rst:501 +#: ../misc/object-conditions/basics.rst:524 +#: ../misc/object-conditions/basics.rst:550 +#: ../misc/object-conditions/basics.rst:572 +#: ../misc/object-conditions/basics.rst:603 +#: ../settings/security/third-party.rst:85 ../settings/system/frontend.rst:54 +#: ../system/maintenance.rst:70 ../system/maintenance.rst:94 +msgid "X" +msgstr "" + +#: ../manage/slas/index.rst:54 +msgid "" +"You can configure :doc:`/manage/overviews` to allow your agents to filter " +"for escalated tickets or those that are about to escalate. By default Zammad " +"comes with an overview that will show all tickets that are either escalated " +"or escalating within the next 10 minutes: ``Escalated Tickets``." +msgstr "" + +#: ../manage/slas/index.rst:61 +msgid "" +"If you have all/most of your tickets covered by SLAs you may consider " +"changing the default sorting of existing overviews by escalation time, " +"instead of creation time." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing overview with escalated tickets" +msgstr "" + +#: ../manage/slas/index.rst:92 +msgid "SLA timings of a ticket" +msgstr "" + +#: ../manage/slas/index.rst:70 +msgid "" +"Ticket zooms provide a timestamp of the next escalation of a ticket. Agents " +"can hover that timestamp and learn about all upcoming escalation stages." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "Screenshot showing the calculated escalation stages" +msgstr "" + +#: ../manage/slas/index.rst:79 +msgid "A fresh ticket without any response by agents." +msgstr "" + +#: ../manage/slas/index.rst:0 +msgid "" +"Screenshot showing the calculated escalation stages after agents\n" +"first response" +msgstr "" + +#: ../manage/slas/index.rst:88 +msgid "A ticket after the agents initial response and a customer response." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:4 +msgid "" +"This page contains some possible example configurations for a SLA we could " +"think of. SLAs in general are very flexible and powerful, below doesn't have " +"to be your standard!" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:10 +#: ../system/core-workflows/learn-by-example.rst:9 +msgid "" +"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" +"they-work` to learn about all the options in detail, then come back here to " +"see them in action." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:14 +msgid "" +"All following SLAs have the same base configurations. They may not use all " +"of them in all samples." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +msgid "**Groups**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:18 +#: ../system/core-workflows/learn-by-example.rst:17 +msgid "Sales" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:19 +#: ../system/core-workflows/learn-by-example.rst:18 +msgid "Support" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:20 +#: ../system/core-workflows/learn-by-example.rst:19 +msgid "2nd Level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "**Attribtues**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:22 +msgid "User / VIP (default, Boolean)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:23 +msgid "" +"Organization / Support-Contract (Single selection field, ``None`` as default " +"value)" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "**Calendar setting**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:26 +msgid "The calendar is set to 8 hours per day, from Monday to Friday." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:28 +msgid "**1. Support contract levels and VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:30 +msgid "" +"This approach uses a combination of contract levels (where any level except " +"for none causes SLA escalations) and VIP customers that can have further " +"priority." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:34 +msgid "" +"The configuration of these SLAs ensures that either fitting support contract " +"levels trigger or the VIP state is being used. They're not overlapping." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:39 +#: ../manage/slas/learn-by-example.rst:100 +msgid "VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:41 +#: ../manage/slas/learn-by-example.rst:102 +msgid "SLA configuration checking if the customer is a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:47 +msgid "Support contract levels" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:49 +msgid "" +"The settings of each support contract level SLA basically are the same. The " +"only setting that differs is the support contract level of each " +"configuration and the SLA timings." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:53 +msgid "" +"For this reason we're showing the bronze level configuration as an example " +"only." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "" +"Screenshot showing SLA configuration for support contract\n" +"level bronze." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:116 +#: ../system/core-workflows/learn-by-example.rst:89 +#: ../system/core-workflows/learn-by-example.rst:101 +#: ../system/integrations/slack.rst:89 +msgid "The result" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:62 +msgid "This approach causes the following SLA timings for each level:" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "" +"If the customer has no VIP state and the organization has a support level" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:68 +msgid "Bronze" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``6 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``40 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:73 +msgid "Silver" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``4 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``32 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:78 +msgid "Gold" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``2 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``24 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "None" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:81 +msgid "This setting has no SLA configuration. Tickets will not escalate." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:86 +#: ../manage/slas/learn-by-example.rst:112 +msgid "If the customer has the VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``1 hour``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Solution time: ``16 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:88 +msgid "**2. VIP customers**" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:92 +msgid "non VIP customers" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:94 +msgid "SLA configuration checking if the customer is not a VIP customer." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Screenshot showing SLA configuration for non-VIP customers." +msgstr "" + +#: ../manage/slas/learn-by-example.rst:116 +msgid "If the customer has no VIP state" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "First response time: ``8 hours``" +msgstr "" + +#: ../manage/slas/learn-by-example.rst:0 +msgid "Update time (for an agent to respond): ``16 hours``" +msgstr "" + +#: ../manage/tags.rst:4 +msgid "With tags, tickets can be categorized and marked." +msgstr "" + +#: ../manage/tags.rst:7 +msgid "How to tag" +msgstr "" + +#: ../manage/tags.rst:9 +msgid "" +"All agents can tag tickets. You can find further information about tagging " +"of tickets on our `user documentation`_." +msgstr "" + +#: ../manage/tags.rst:16 +msgid "Tag-Overviews" +msgstr "" + +#: ../manage/tags.rst:18 +msgid "You can list all the marked tickets by tag in different ways:" +msgstr "" + +#: ../manage/tags.rst:20 +msgid "" +"by providing an appropriate overview Create a new overview and select \"Tag " +"contains ...\" as condition. You can find further information in :doc:" +"`overviews`" +msgstr "" + +#: ../manage/tags.rst:24 +msgid "" +"by a search-query Enter e. g.: ``tags:americano`` in the search mask and you " +"will receive all tickets that have been tagged accordingly. For a collected " +"listing, click on \"Show Search Details\" under the search box:" +msgstr "" + +#: ../manage/tags.rst:31 +msgid "" +"by clicking on the tag in the Tag Management Area In the Tag Management you " +"can find an overview of existing tags used in the system (and a counter how " +"often they are used):" +msgstr "" + +#: ../manage/tags.rst:37 +msgid "" +"For more information about the individual tags, just click on the blue " +"counter:" +msgstr "" + +#: ../manage/tags.rst:42 +msgid "" +"Select one of the tickets that appears below the search box or get a " +"complete overview of all tickets by clicking on \"Show Search Details\":" +msgstr "" + +#: ../manage/tags.rst:49 +msgid "Tag Management Area" +msgstr "" + +#: ../manage/tags.rst:51 +msgid "" +"Here it can also (in addition to the overview - as described above) be set " +"whether the agents are allowed to add tags themselves or not (in the left " +"upper corner)." +msgstr "" + +#: ../manage/tags.rst:55 +msgid "You can add more tags or delete them." +msgstr "" + +#: ../manage/templates.rst:2 +msgid "Templates" +msgstr "" + +#: ../manage/templates.rst:4 +msgid "" +"Templates allow you to create tickets at a rapid speed by defining a ticket " +"template for recurring tickets." +msgstr "" + +#: ../manage/templates.rst:7 +msgid "**😖 Sounds familiar**" +msgstr "" + +#: ../manage/templates.rst:9 +msgid "" +"Right! Prior Zammad 5.3 ticket templates were managed entirely within the " +"ticket zoom." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "This has changed:" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "" +"Your agents by default no longer have permission to manage templates by " +"default. However, they can always *load* existing templates into their new " +"ticket dialogue." +msgstr "" + +#: ../manage/templates.rst:None +msgid "Screenshot showing Zammad's (ticket) template management page" +msgstr "" + +#: ../manage/templates.rst:21 +msgid "⚠️ Limitation ahead" +msgstr "" + +#: ../manage/templates.rst:23 +msgid "Please note that ticket templates do not allow the use of variables." +msgstr "" + +#: ../manage/templates.rst:26 +msgid "Managing templates" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Adding new template" +msgstr "" + +#: ../manage/templates.rst:29 +msgid "Use the *New Template* button to start creating a new template." +msgstr "" + +#: ../manage/templates.rst:32 +msgid "" +"Select a meaningful template name. This name will be shown to your agents " +"during ticket creation (within *Select Template*)." +msgstr "" + +#: ../manage/templates.rst:36 +msgid "" +"Within actions, Zammad will provide all available ticket attributes. This " +"allows you to create granular templates with the information you need." +msgstr "" + +#: ../manage/templates.rst:41 +msgid "" +"Set any currently active ticket template to ``inactive`` if you don't need " +"it momentarily. This allows you to keep the template for e.g. seasonal " +"reasons without providing it as an option to your agents." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Screenshot showing the template configuration" +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Editing templates" +msgstr "" + +#: ../manage/templates.rst:49 +msgid "" +"If your template no longer fits your need or contains errors, simply click " +"on the template name to edit it." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Cloning templates" +msgstr "" + +#: ../manage/templates.rst:53 +msgid "" +"Zammad allows you to clone existing templates and continue your new template " +"from there." +msgstr "" + +#: ../manage/templates.rst:56 +msgid "" +"To do so, use *⋮ Actions* of the desired template in your list and choose " +"*Clone*. A new template modal will open with attributes prefilled." +msgstr "" + +#: ../manage/templates.rst:0 +msgid "Removing templates" +msgstr "" + +#: ../manage/templates.rst:60 +msgid "" +"If you no longer require a specific template, use *⋮ Actions* in the list " +"and choose *Delete*." +msgstr "" + +#: ../manage/templates.rst:65 +msgid "Removals are permanent. ☠️" +msgstr "" + +#: ../manage/text-modules.rst:2 +msgid "Text Modules" +msgstr "" + +#: ../manage/text-modules.rst:6 +msgid "" +"Beside text modules Zammad also allows you to use `Ticket Templates for " +"ticket creation`_." +msgstr "" + +#: ../manage/text-modules.rst:12 +msgid "" +"Text modules can be edited in the admin interface under Manage --> Text " +"modules. Here you will find text snippets already created in the standard " +"version, which can be extended as needed." +msgstr "" + +#: ../manage/text-modules.rst:18 +msgid "Here you can add new text modules, delete or edit them." +msgstr "" + +#: ../manage/text-modules.rst:20 +msgid "Creating keywords makes it easier to find the right text module." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "You can find text modules either by their name or keyword." +msgstr "" + +#: ../manage/text-modules.rst:25 +msgid "" +"If needed, you can restrict text modules to specific groups. With this, you " +"can easilly keep text module lists short and dedicate specific texts to " +"where they belong." +msgstr "" + +#: ../manage/text-modules.rst:29 +msgid "" +"You can adjust the group memberships for text modules at any time. This " +"allows you to have the text module available globally (no groups selected) " +"or one or several specific groups." +msgstr "" + +#: ../manage/text-modules.rst:None +msgid "Example: Restricting text modules to 2nd Level group only." +msgstr "" + +#: ../manage/text-modules.rst:36 +msgid "" +"To select placeholders from a list, just enter ``::`` in the text block. The " +"list can be searched with the arrow keys after inputting keywords or " +"shortcuts. All text modules can be used in articles as well as in the chat." +msgstr "" + +#: ../manage/text-modules.rst:42 +msgid "" +"You can find more information on how to use text modules on our `user " +"documentation`_." +msgstr "" + +#: ../manage/text-modules.rst:49 +msgid "" +"If text modules are to be grouped, this can be done using shortcuts. Example " +"country codes:" +msgstr "" + +#: ../manage/text-modules.rst:52 +msgid "Text modules are created for the group Germany as follows:" +msgstr "" + +#: ../manage/text-modules.rst:54 +msgid "Ger_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:55 +msgid "Ger_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:56 +msgid "..." +msgstr "" + +#: ../manage/text-modules.rst:58 +msgid "for Austrian-Snippets:" +msgstr "" + +#: ../manage/text-modules.rst:60 +msgid "Aut_Textmodule1" +msgstr "" + +#: ../manage/text-modules.rst:61 +msgid "Aut_Textmodule2" +msgstr "" + +#: ../manage/text-modules.rst:63 +msgid "thus only the relevant text modules are displayed for each country." +msgstr "" + +#: ../manage/text-modules.rst:65 +msgid "" +"The example text modules below use :doc:`/system/variables` to dynamically " +"insert information like the customer’s or agent’s names." +msgstr "" + +#: ../manage/text-modules.rst:68 +msgid "**Examples of snippets are**::" +msgstr "" + +#: ../manage/text-modules.rst:78 +msgid "Of course you can also use multi line snippets." +msgstr "" + +#: ../manage/text-modules.rst:81 +msgid "Delete or clone text modules" +msgstr "" + +#: ../manage/text-modules.rst:83 +msgid "" +"Often similar text modules have to be created or unnecessary ones deleted. " +"For these cases you can click on the 3 points in the text module overview on " +"the right side and select the corresponding action:" +msgstr "" + +#: ../manage/text-modules.rst:89 +msgid "" +"When cloning, text modules with all attributes are duplicated and can be " +"edited later." +msgstr "" + +#: ../manage/text-modules.rst:93 +msgid "Import of text modules via CSV file" +msgstr "" + +#: ../manage/text-modules.rst:95 +msgid "" +"With the import action (since Zammad 2.5) you can download a sample CSV file " +"and upload your own CSV file." +msgstr "" + +#: ../manage/text-modules.rst:98 +msgid "" +"To reduce the error rate of unwanted mass changes, a test import is carried " +"out first and a summary appears at the end. If you agree with the summary, " +"the CSV import will be executed." +msgstr "" + +#: ../manage/time-accounting.rst:2 +msgid "Time Accounting" +msgstr "" + +#: ../manage/time-accounting.rst:4 +msgid "" +"If you want to know how much time you need for your each project or ticket, " +"enable time accounting (turn on the switch on the top left side of the page)." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting management page in Zammad" +msgstr "" + +#: ../manage/time-accounting.rst:11 +msgid "How it works" +msgstr "" + +#: ../manage/time-accounting.rst:13 +msgid "" +"Zammad's time accounting uses ticket selectors (filters) to check if a " +"ticket is applicable for time accounting or not. If a ticket applies for " +"accounting, Zammad will request the agent to provide how much time was " +"needed to process the current ticket step." +msgstr "" + +#: ../manage/time-accounting.rst:20 +msgid "" +"In order for Zammad to bring up the time accounting dialogue to an agent, " +"the agent has to update the ticket together with any article type. The " +"article part is mandatory." +msgstr "" + +#: ../manage/time-accounting.rst:24 +msgid "" +"However, the time accounting dialogue is not mandatory and can be cancelled " +"by your agents if needed. You cannot enforce time accounting." +msgstr "" + +#: ../manage/time-accounting.rst:27 +msgid "" +"If a ticket no longer applies for time accounting, the already accounted " +"time is not lost." +msgstr "" + +#: ../manage/time-accounting.rst:32 +msgid "" +"The selector applies to the ticket state before any attribute changes have " +"been saved. That means if your agent is e.g. going to close a ticket " +"alongside writing an article, the ticket selector has to match the ticket " +"state before closing for the time accounting dialog to appear." +msgstr "" + +#: ../manage/time-accounting.rst:None +msgid "Time accounting ticket selectors" +msgstr "" + +#: ../manage/time-accounting.rst:44 +msgid "Reviewing accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:46 +msgid "" +"Below the selector configuration, Zammad provides an accounted time section " +"which will contain all accounted times for your tickets. Accounted times are " +"displayed per years and months." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Having tickets that are overlapping several months?" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "" +"No problem! Zammad provides *time units* and *time units total* to allow " +"partial billing." +msgstr "" + +#: ../manage/time-accounting.rst:62 +msgid "Select the right month" +msgstr "" + +#: ../manage/time-accounting.rst:57 +msgid "" +"Usually you want to bill accounted time of other months than the current " +"one. Just select the relevant year and month to receive the accounted times " +"and ticket information" +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Screenshot showing a selection for year and month on time accounting" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "Tickets and their accounted time" +msgstr "" + +#: ../manage/time-accounting.rst:65 +msgid "" +"Zammad allows you to receive the accounted information just like you need " +"them. For this you currently have four options to view and also download the " +"relevant data as CSV." +msgstr "" + +#: ../manage/time-accounting.rst:69 +msgid "" +"To download the CSV data, use the arrow down ⇩ right next to each heading (e." +"g. \"Ticket\")." +msgstr "" + +#: ../manage/time-accounting.rst:74 +msgid "🤓 Of course you can also automate this with API calls." +msgstr "" + +#: ../manage/time-accounting.rst:89 +msgid "Activity" +msgstr "" + +#: ../manage/time-accounting.rst:77 +msgid "" +"This filter works similar to the ticket filter, with one exception: You'll " +"find each *individual* time accounting step of your agents. This is what " +"you'd also see in the tickets history before Zammad 5.2." +msgstr "" + +#: ../manage/time-accounting.rst:81 ../manage/time-accounting.rst:94 +#: ../manage/time-accounting.rst:115 +msgid "In this list you'll see the following ticket information:" +msgstr "" + +#: ../manage/time-accounting.rst:83 ../manage/time-accounting.rst:96 +#: ../settings/ticket.rst:71 +msgid "Number" +msgstr "" + +#: ../manage/time-accounting.rst:85 ../manage/time-accounting.rst:98 +#: ../manage/time-accounting.rst:119 ../manage/time-accounting.rst:117 +msgid "Customer" +msgstr "" + +#: ../manage/time-accounting.rst:86 ../manage/time-accounting.rst:99 +#: ../manage/time-accounting.rst:118 +msgid "Organization of customer (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:87 +msgid "Agent that accounted the time" +msgstr "" + +#: ../manage/time-accounting.rst:88 ../manage/time-accounting.rst:101 +#: ../manage/time-accounting.rst:119 +msgid "Time units accounted in the current month" +msgstr "" + +#: ../manage/time-accounting.rst:89 ../manage/time-accounting.rst:103 +#: ../manage/webhook/log.rst:34 +msgid "Created at" +msgstr "" + +#: ../manage/time-accounting.rst:108 ../settings/ticket.rst:2 +#: ../system/variables/ticket.rst:2 +msgid "Ticket" +msgstr "" + +#: ../manage/time-accounting.rst:92 +msgid "This filter contains all relevant tickets from the selected month." +msgstr "" + +#: ../manage/time-accounting.rst:100 +msgid "Agent currently assigned (ticket owner)" +msgstr "" + +#: ../manage/time-accounting.rst:102 +msgid "Time units total (time accounted during ticket life)" +msgstr "" + +#: ../manage/time-accounting.rst:104 +msgid "Closed at (if applicable)" +msgstr "" + +#: ../manage/time-accounting.rst:108 +msgid "The CSV file of this filter provides all ticket meta information." +msgstr "" + +#: ../manage/time-accounting.rst:111 +msgid "" +"This provides you a per user filter on accounted time units. Each user has a " +"total of time accounted in the current month (over all applicable tickets)." +msgstr "" + +#: ../manage/time-accounting.rst:129 ../settings/branding.rst:13 +#: ../system/objects/permissions.rst:54 +msgid "Organization" +msgstr "" + +#: ../manage/time-accounting.rst:122 +msgid "" +"This provides a list of all organizations where customers have caused " +"accounted time in that month." +msgstr "" + +#: ../manage/time-accounting.rst:127 +msgid "" +"You can also see entries for customers that are part of an primary " +"organization. Users without organization can be found in the Customer filter." +msgstr "" + +#: ../manage/time-accounting.rst:0 +msgid "Time accounting view with time accounted filters" +msgstr "" + +#: ../manage/time-accounting.rst:135 +msgid "" +"Each heading allows you to download the CSV versions of the provided view " +"via the downwards arrow." +msgstr "" + +#: ../manage/trigger.rst:2 +msgid "Triggers" +msgstr "" + +#: ../manage/trigger.rst:4 +msgid "" +"Use triggers to set up all kinds of 🎛️ **if-this-then-that** automation " +"workflows." +msgstr "" + +#: ../manage/trigger.rst:7 +msgid "" +"For ⏳ **every-so-often** automation workflows, try :doc:`schedulers ` instead." +msgstr "" + +#: ../manage/trigger.rst:10 +msgid "" +"The first thing to know about triggers is that **you're already using " +"them**. From the moment you set up Zammad, it starts sending auto-replies to " +"all incoming emails. Recognize this line?" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply notification in ticket view" +msgstr "" + +#: ../manage/trigger.rst:17 +msgid "" +"It means that the ticket is from an incoming customer email, and that the " +"customer received this message in response:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of auto-reply in customer’s inbox" +msgstr "" + +#: ../manage/trigger.rst:23 +msgid "" +"This auto-reply message is a **trigger**. You can disable it, modify it, or " +"create new ones for all sorts of automation tasks on the Trigger page of the " +"admin panel:" +msgstr "" + +#: ../manage/trigger.rst:None +msgid "Screenshot of “Triggers” page in admin panel" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:4 +msgid "" +"Triggers consist of three parts: **activators**, **conditions** and " +"**changes**. Activator defines “when the question is asked?”. Conditions " +"answer the question, “when should this trigger fire?” Changes answer the " +"question, “what should happen when it does?”" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:9 +msgid "" +"Triggers are evaluated in alphabetical order, by **name.** In some " +"situations triggers might be the wrong choice, see :doc:`/manage/trigger/" +"limitations` for more information." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:13 +msgid "**🤓 Email trigger behavior can be manipulated**" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:15 +msgid "" +"Please have a look at :doc:`/channels/email/email-headers` in case this is a " +"relevant use case for you." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:19 +msgid "Activators" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:21 +msgid "Triggers support two types of activators:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:23 +msgid "" +"**Action** is triggered by some actor. Either a user creating or updating " +"the ticket. Or an external action, e.g. an email coming in." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:26 +msgid "" +"**Time event** is triggered at a specific time. When a certain event is " +"reached, e.g. ticket pending time." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:29 +msgid "**Action** activator may evaluate **Conditions** in two modes:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:31 +msgid "" +"**Selective** execution checks if any property that is included in " +"conditions was updated. If the action was other than update, it checks if " +"conditions match." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:35 +msgid "" +"A selective action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was changed to **1 low** or got an new article in that " +"priority state." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:39 +msgid "" +"**Always** execution checks if the current state of the ticket in question " +"matches conditions." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:43 +msgid "" +"An always action trigger which is listening on the priority **1 low** will " +"trigger if the ticket was moved to another group while priority was set **1 " +"low**." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:47 +msgid "" +"**Time event** activator simply checks if **Conditions** match. This is the " +"same behavior as Action-based activator's „Always“ mode." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:50 +msgid "When creating a trigger, choose activator here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "Conditions" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:57 +msgid "When creating a trigger, define your conditions here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:61 +msgid "Trigger conditions must match as configured for the trigger to fire." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:68 +msgid "When creating a trigger, define your changes here:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:72 +msgid "" +"A trigger can do the following things once its conditions have been met:" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Modify the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:75 +msgid "" +"*e.g.,* Escalate its priority, close it, reassign it, rename it, add tags, " +"etc." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:78 +msgid "" +"Date & time attributes (like **Pending till**) can be specified in " +"*absolute* or *relative* terms." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:83 +msgid "" +"You can also combine static text with placeholders for text fields. Remember " +"that the placeholders' values have to be known during trigger runtime." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:87 +msgid "Learn more about :doc:`/system/variables`." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "Send an email or SMS" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:90 +msgid "" +"Either to the customer, the agent who owns the ticket, or every agent in the " +"system." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:95 +msgid "" +"Sending emails allows you to include the attachments of the triggering " +"article if required." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid ":doc:`Fire a webhook `" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:98 +msgid "" +"Connect Zammad to another web service or application to give it live updates " +"about new tickets." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:102 +msgid "Add internal or public notes to the ticket" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:101 +msgid "" +"This allows you to help your agents with specific information if needed. (e." +"g. automated changes a trigger applied to the ticket)" +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:104 +msgid "" +"In order to send emails with Triggers, you need to configure an email " +"address for the group the trigger is working in. If you don't, Zammad will " +"skip the Trigger completely." +msgstr "" + +#: ../manage/trigger/how-do-they-work.rst:108 +msgid "" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"variables`, which can be used to build highly-customized message templates." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:4 +msgid "" +"To get you up and running quickly, here are some examples of the kinds of " +"automation tasks you can set up with triggers." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:7 +msgid "" +"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"manage/trigger/how-do-they-work` to learn about all the options in detail, " +"then come back here to see them in action." +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:12 +msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:16 +msgid "" +"Emma Taylor is responsible for all sales internally, so if a new ticket has " +"the word “order” in the subject, assign it to her and make sure it’s set " +"with a high priority:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:22 +msgid "Send an auto-reply email to *any customer* who responds to a ticket:" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:26 +msgid "📨 **Not all automated messages come from triggers!**" +msgstr "" + +#: ../manage/trigger/learn-by-example.rst:28 +msgid "" +"For instance, when *agents* receive a system email about a newly created " +"ticket, that’s built into the system itself. If you need to customize those, " +"you will have to :doc:`manually edit files on your server `." +msgstr "" + +#: ../manage/trigger/limitations.rst:4 +msgid "" +"It's important to understand when a trigger can be used and when it's better " +"to use e.g. Zammad's :doc:`/manage/scheduler` or :doc:`postmaster filters `." +msgstr "" + +#: ../manage/trigger/limitations.rst:8 +msgid "" +"While the creation of a ticket is straight forward, updating an existing " +"ticket is a bit trickier. In terms of triggers, a ticket is only updated if " +"you press the update button on the lower right of a ticket. Adding tags to a " +"ticket or switching articles visibility **is no ticket update**." +msgstr "" + +#: ../manage/trigger/limitations.rst:14 +msgid "" +"Also keep in mind that we're always only working on the last article. This " +"means you can't trigger for past articles. Triggers always handle the " +"current ticket attributes and the article (if applicable) that cause the " +"trigger to fire." +msgstr "" + +#: ../manage/trigger/limitations.rst:19 +msgid "" +"If your use case doesn't fit in above possibilities, you might want to have " +"a look at Zammad's :doc:`/manage/scheduler`." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:2 +msgid "System Notifications" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:4 +msgid "" +"System notifications can only be customized on **self-hosted installations**." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:11 +msgid "" +"Unlike the automated emails you can set up using :doc:`/manage/trigger` or " +"the :doc:`/manage/scheduler`, these notifications are built into Zammad " +"itself: if you need to customize them, you will have to modify some of the " +"files on your server." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:18 +msgid "When are they sent?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:20 +msgid "**All users** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:22 +msgid "password change requests" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:23 +msgid ":ref:`automatic-account-linking-notification` on initial login" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:25 +msgid "**Staff (admins & agents)** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:27 +msgid "logins from a new device" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:28 +msgid "logins from a new country" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:30 +msgid "**Agents** are notified of:" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:32 +msgid "new tickets" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:33 +msgid "ticket updates" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:34 +msgid "“ticket pending” reminders" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:35 +msgid "SLA violations (before and after the deadline)" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:37 +msgid "" +"Daily reminder emails are sent at midnight (of the Zammad system timezone) " +"for all unresolved “ticket pending” reminders and SLA violations." +msgstr "" + +#: ../manage/trigger/system-notifications.rst:41 +msgid "How can I customize them?" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:43 +msgid "" +"Inside your Zammad directory (usually ``/opt/zammad``), email templates for " +"various events are stored inside the ``/app/views/mailer`` directory, named " +"according to the language they’re written in. Thus, ::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:49 +msgid "" +"is the German-language template used to notify agents whenever a new ticket " +"is created. To modify this template, create another file with the same name " +"and add a ``.custom`` suffix::" +msgstr "" + +#: ../manage/trigger/system-notifications.rst:55 +msgid "" +"Now, this file will be used instead of the original when sending " +"notification emails in German." +msgstr "" + +#: ../manage/users/index.rst:2 +msgid "Users" +msgstr "" + +#: ../manage/users/index.rst:4 +msgid "" +"Depending on your organization’s IT capabilities, users can be managed " +"individually or in bulk, or even synchronized with third-party directory " +"services." +msgstr "" + +#: ../manage/users/index.rst:13 +msgid "The simplest way to manage users is directly in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "Learn more about managing users..." +msgstr "" + +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 +msgid "😲 **Customers get their own user accounts, too?**" +msgstr "" + +#: ../manage/users/index.rst:31 +msgid "" +"Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " +"communicates through the system." +msgstr "" + +#: ../manage/users/index.rst:34 +msgid "" +"Why? It helps us do things like show all tickets from a certain customer." +msgstr "" + +#: ../manage/users/index.rst:36 +msgid "" +"How? Zammad checks the sender of every incoming message at every inbox it " +"monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " +"account!" +msgstr "" + +#: ../manage/users/index.rst:41 +msgid "" +"(Your customers never need to set a password. Of course, they can if they " +"want to, but the account will be there even if they never use it.)" +msgstr "" + +#: ../manage/users/index.rst:48 +msgid "Reference Guide: User Details" +msgstr "" + +#: ../manage/users/index.rst:50 +msgid "" +"Most of the attributes you can set on user accounts are self-explanatory. " +"The ones that aren’t are described below." +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "The edit user dialog, showing the various user detail fields" +msgstr "" + +#: ../manage/users/index.rst:58 +msgid "User details can be set in the **New/Edit User** dialog." +msgstr "" + +#: ../manage/users/index.rst:62 +msgid "" +"In most cases, agents can, too (using the `new ticket dialog`_, `search " +"bar`_ or the `ticket pane`_)." +msgstr "" + +#: ../manage/users/index.rst:88 +msgid "👤 Login" +msgstr "" + +#: ../manage/users/index.rst:73 +msgid "" +"A user’s email and login may differ, but **either one can be used to sign in." +"**" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "The user overview, showing logins in the first column" +msgstr "" + +#: ../manage/users/index.rst:82 +msgid "" +"User logins are **not** shown in the New/Edit User dialog, but they are " +"visible from the user overview." +msgstr "" + +#: ../manage/users/index.rst:85 +msgid "" +"This attribute **cannot** be set via the Admin Panel. Instead, use the " +"`Zammad console `_, " +"the `REST API `_, or :doc:" +"`CSV import `." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "🔑 Password" +msgstr "" + +#: ../manage/users/index.rst:91 +msgid "" +"Yes, administrators really do have the power to change other users’ " +"passwords." +msgstr "" + +#: ../manage/users/index.rst:93 +msgid "(Agents do not, though.)" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "🏢 Organization" +msgstr "" + +#: ../manage/users/index.rst:96 +msgid "" +":doc:`/manage/organizations/index` are a way to group customers together " +"(usually, members of the same company). This allows you to do things like " +"view all tickets for that company or set up special :doc:`/manage/trigger` " +"that fire only for those customers." +msgstr "" + +#: ../manage/users/index.rst:101 +msgid "" +"🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" +msgstr "" + +#: ../manage/users/index.rst:104 +msgid "To add one, go to **Manage > Organizations** in the Admin Panel." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "🏤 Secondary Organizations" +msgstr "" + +#: ../manage/users/index.rst:107 +msgid "" +"This option allows you to assign more organizations, in addition to the " +"user's primary organization." +msgstr "" + +#: ../manage/users/index.rst:110 +msgid "" +"Secondary organizations behave the same like the primary ones with one " +"exception: Secondaries are not as highlighted like their primaries." +msgstr "" + +#: ../manage/users/index.rst:115 +msgid "" +"Listings for all organizational tickets are not affected by this. Zammad " +"will mix primary and secondary organization tickets together." +msgstr "" + +#: ../manage/users/index.rst:120 +msgid "" +"While the number of secondary organizations is not limited directly, you may " +"want to keep this to a reasonable number of organizations." +msgstr "" + +#: ../manage/users/index.rst:123 +msgid "30-40 organizations at maximum *should* be good enough." +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "👑 VIP" +msgstr "" + +#: ../manage/users/index.rst:126 +msgid "" +"This flag is a way for your team to indicate high-status customers. Just as " +"with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" +"manage/scheduler` jobs, :doc:`/manage/slas/index`, and :doc:`/manage/" +"overviews` just for VIPs." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Ticket view showing a VIP user’s avatar with a crown on it" +msgstr "" + +#: ../manage/users/index.rst:136 +msgid "VIPs are displayed with a crown above their avatars." +msgstr "" + +#: ../manage/users/index.rst:141 +msgid "" +"😵 **Are you using the Note field to keep track of your own “custom” user " +"attributes?**" +msgstr "" + +#: ../manage/users/index.rst:144 +msgid "Wish you could add your own fields to the New/Edit User dialog?" +msgstr "" + +#: ../manage/users/index.rst:149 +msgid "" +"Disabling this flag is a soft alternative to deleting a user. So what’s the " +"difference?" +msgstr "" + +#: ../manage/users/index.rst:152 +msgid "" +"There is no way to restore a deleted user; inactive users can be reactivated " +"at any time." +msgstr "" + +#: ../manage/users/index.rst:155 +msgid "" +"When a user is deleted, all their associated tickets are lost, as well; " +"deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:158 +msgid "Inactive users still appear in search results:" +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "An inactive user displayed in a customer search list" +msgstr "" + +#: ../manage/users/index.rst:164 +msgid "" +"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +"users are greyed out." +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "🔓 Permissions" +msgstr "" + +#: ../manage/users/index.rst:170 +msgid "" +"Under this heading, you can manage two separate (but related) user details:" +msgstr "" + +#: ../manage/users/index.rst:172 +msgid "" +":doc:`/manage/roles/index` dictate what users can do in the system. If you " +"need to grant someone privileges to edit the knowledge base or access part " +"of the admin panel, roles are the answer." +msgstr "" + +#: ../manage/users/index.rst:176 +msgid "" +":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " +"with. If someone’s not receiving notifications for incoming tickets or can’t " +"be assigned a ticket, group access levels are likely to blame." +msgstr "" + +#: ../manage/users/index.rst:0 +msgid "Permissions in the edit user dialog" +msgstr "" + +#: ../manage/users/index.rst:187 +msgid "" +"**Top:** A user’s roles decide what kinds of actions they can perform and " +"which :doc:`groups ` they belong to. **Bottom:** Group " +"assignments can alternately be set on a per-user basis." +msgstr "" + +#: ../manage/users/index.rst:191 +msgid "**🤔 Huh? I don’t see the group access table...**" +msgstr "" + +#: ../manage/users/index.rst:193 +msgid "" +"The group access table is only visible in **agent profiles**, when there is " +"**more than one active group** in the system." +msgstr "" + +#: ../manage/users/via-csv-import.rst:2 +msgid "Managing users via CSV Import" +msgstr "" + +#: ../manage/users/via-csv-import.rst:16 +msgid "" +"CSV import provides one-off batch processing of user records. For " +"persistent, automated user synchronization, consider integration with a " +"third-party directory system like :doc:`LDAP / Active Directory ` or :doc:`Exchange `." +msgstr "" + +#: ../manage/users/via-csv-import.rst:25 +msgid "" +"Use the link at the bottom of the CSV import dialog (**“Example CSV file for " +"download”**) to see how Zammad expects you to format your user data." +msgstr "" + +#: ../manage/users/via-csv-import.rst:30 +msgid "Step 2: Export your user data to .csv" +msgstr "" + +#: ../manage/users/via-csv-import.rst:35 +msgid "the ``firstname`` and ``lastname`` attributes are **required**; and" +msgstr "" + +#: ../manage/users/via-csv-import.rst:50 +msgid "" +"Once your raw user data has been submitted, Zammad will perform a test run " +"to compute the number of affected records:" +msgstr "" + +#: ../manage/users/via-csv-import.rst:62 +msgid "" +"Records are updated when the imported data contains an ``email`` or " +"``login`` that matches an existing user account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:2 +msgid "Managing users via the admin panel" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:4 +msgid "The “Users” panel provides tools to manually manage user accounts." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being created." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:11 +msgid "" +"Click the **New User** button to open the New User dialog, or click on an " +"existing user to edit." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:14 +msgid "" +"See :ref:`user-details-reference` for help with the New/Edit User dialog." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:26 +msgid "🗑️ Deleting users" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing a user being selected for deletion." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:46 +msgid "🔎 Filtering the user list" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "" +"Screencast showing the user list being filtered by available user roles." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:33 +msgid "" +"Use the 🔎 **Search for users** bar and the **Roles** buttons to filter the " +"list. You may search by name, email, or any other user attribute." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:36 +msgid "🐞 **Known bug**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:38 +msgid "" +"The search list displays up to 50 users, from newest to oldest. That means " +"that if there are more than 50 results, the user you’re searching for might " +"not be shown." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:42 +msgid "This is a `known bug`_ with a fix underway." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:57 +msgid "🔒 Unlock locked user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing how to unlock user accounts" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:53 +msgid "" +"Use the ⋮ **Actions** menu to unlock accounts after too many failed logins. " +"Locked accounts are indicated with a 🔒 lock icon on the left side." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:87 +msgid "🏴‍☠️ Taking over a user’s session" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:0 +msgid "Screencast showing an admin switching to the users perspective" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:64 +msgid "Use the ⋮ **Actions** menu to 👁️ **View from user’s perspective**." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:66 +msgid "" +"The **View from user’s perspective** button allows you to “hijack” another " +"user’s session and confirm firsthand what they can and can’t do (or see) " +"when they’re logged in." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:71 +msgid "" +"This is especially useful when you need to verify that you’ve set up custom " +"permissions correctly for non-admin users." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:74 +msgid "**⚠ With great power comes with great responsibility.**" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:76 +msgid "" +"This feature is not a simulation; entering this mode will boot the user from " +"their session, and any actions you take (responding to tickets, changing " +"passwords, :doc:`logging hours worked `) will " +"actually be performed from the user’s account." +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:83 +msgid "(On the other hand, if the user logs back in, you’ll be booted, too.)" +msgstr "" + +#: ../manage/users/via-the-admin-panel.rst:85 +msgid "" +"When finished, use the **Back to my view ✕** button at the top of the page. " +"If you try to exit by logging out, the “hijacked” user session will be " +"restored when you log back in." +msgstr "" + +#: ../manage/webhook.rst:2 +msgid "Webhook" +msgstr "" + +#: ../manage/webhook.rst:4 +msgid "" +"Webhooks are a way to integrate Zammad with other web services or " +"applications, allowing them to subscribe to live updates about tickets " +"instead of having to poll the Zammad server every *n* minutes." +msgstr "" + +#: ../manage/webhook.rst:8 +msgid "⌛ **Webhooks may not arrive immediately.**" +msgstr "" + +#: ../manage/webhook.rst:10 +msgid "" +"Webhooks are sent out with the same priority and order as email triggers. If " +"webhook dispatch fails (*e.g.,* because the receiving server is " +"misconfigured), Zammad will retry up to four times." +msgstr "" + +#: ../manage/webhook.rst:16 +msgid "" +"Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/" +"scheduler`." +msgstr "" + +#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:18 +msgid "How does it work?" +msgstr "" + +#: ../manage/webhook.rst:22 +msgid "" +"Under the hood, Zammad sends a POST request to a third-party URL (“API " +"endpoint”) you specify in the New Webhook dialog. The application server " +"behind this URL/endpoint must be configured to receive messages from Zammad " +"and handle the provided payload accordingly." +msgstr "" + +#: ../manage/webhook.rst:27 +msgid "" +"Webhooks can be created both from scratch and from pre-defined templates." +msgstr "" + +#: ../manage/webhook.rst:29 +msgid "" +"When created from scratch, regular webhook payloads by default contain the " +"following JSON data about new/updated tickets:" +msgstr "" + +#: ../manage/webhook.rst:32 +msgid "ticket attributes/metadata" +msgstr "" + +#: ../manage/webhook.rst:33 +msgid "*all* associated articles" +msgstr "" + +#: ../manage/webhook.rst:34 +msgid "associated users (*e.g.* article senders, owners, etc.)" +msgstr "" + +#: ../manage/webhook.rst:35 +msgid "associated user roles" +msgstr "" + +#: ../manage/webhook.rst:36 +msgid "associated user organizations (if applicable)" +msgstr "" + +#: ../manage/webhook.rst:37 +msgid "associated groups" +msgstr "" + +#: ../manage/webhook.rst:39 +msgid "" +"On the other hand, pre-defined webhooks are designed to work with specific " +"services, containing special payloads that these services understand." +msgstr "" + +#: ../manage/webhook.rst:42 +msgid "" +"In both cases, however, it is possible to further customize the webhook " +"payload to your own needs." +msgstr "" + +#: ../manage/webhook/add.rst:2 +msgid "Adding Webhooks" +msgstr "" + +#: ../manage/webhook/add.rst:4 +msgid "" +"Webhooks are defined globally. This allows you to use one specific endpoint " +"for several triggers or schedulers." +msgstr "" + +#: ../manage/webhook/add.rst:7 +msgid "**🦻 Default Zammad webhook payloads are specific**" +msgstr "" + +#: ../manage/webhook/add.rst:9 +msgid "" +"Keep in mind that the remote site has to be able to understand the default " +"webhook payload Zammad is sending. Simply throwing the default payload at a " +"webhook endpoint may not have the desired result!" +msgstr "" + +#: ../manage/webhook/add.rst:13 +msgid "See `Custom Payload`_ for a way to customize webhook payloads." +msgstr "" + +#: ../manage/webhook/add.rst:15 +msgid "To add a new regular webhook, use the big green **New Webhook** button." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "Modal showing webhook configuration" +msgstr "" + +#: ../manage/webhook/add.rst:22 +msgid "" +"For a pre-defined webhook, click on the arrow button to the right and choose " +"**Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/add.rst:None +#: ../manage/webhook/examples/mattermost-notifications.rst:None +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Pre-defined Webhook button" +msgstr "" + +#: ../manage/webhook/add.rst:30 +msgid "Next, select the pre-defined webhook you want and click **Next**." +msgstr "" + +#: ../manage/webhook/add.rst:None +msgid "New pre-defined webhook modal" +msgstr "" + +#: ../manage/webhook/add.rst:37 +msgid "**⚠️ Adding a new Webhook is not enough**" +msgstr "" + +#: ../manage/webhook/add.rst:39 +msgid "" +"You must in addition, add a :doc:`Trigger ` or :doc:" +"`Scheduler ` that references the Webhook!" +msgstr "" + +#: ../manage/webhook/add.rst:42 +msgid "You can configure the following information for webhooks:" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "Name (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:45 +msgid "This name will be displayed within trigger and scheduler selections." +msgstr "" + +#: ../manage/webhook/add.rst:55 +msgid "Endpoint (mandatory)" +msgstr "" + +#: ../manage/webhook/add.rst:48 +msgid "Webhook endpoint Zammad sends its payload to." +msgstr "" + +#: ../manage/webhook/add.rst:52 +msgid "" +"Zammad ignores basic authentication parameters. See below how to configure :" +"ref:`username ` and :ref:`password ` via separate fields." +msgstr "" + +#: ../manage/webhook/add.rst:68 +msgid "HMAC SHA1 Signature Token" +msgstr "" + +#: ../manage/webhook/add.rst:58 +msgid "" +"If set all sent webhooks contain a `x-hub-signature` header allowing the " +"remote site to verify the request." +msgstr "" + +#: ../manage/webhook/add.rst:61 +msgid "**🔐 Security note**" +msgstr "" + +#: ../manage/webhook/add.rst:63 +msgid "" +"This *does not* encrypt the payload. Use HTTPS connections to secure the " +"communication. It contains a HMAC signature of the body of the webhook " +"request" +msgstr "" + +#: ../manage/webhook/add.rst:67 +msgid "" +"`Learn more about HUB-Signatures `_" +msgstr "" + +#: ../manage/webhook/add.rst:72 +msgid "SSL verify" +msgstr "" + +#: ../manage/webhook/add.rst:71 +msgid "" +"Defaults to ``yes`` - if you're using unsecure self signed certificates set " +"this option to ``no``." +msgstr "" + +#: ../manage/webhook/add.rst:75 +msgid "_`HTTP Basic Authentication Username`" +msgstr "" + +#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +msgid "" +"Set this if the endpoint requires HTTP basic authentication credentials." +msgstr "" + +#: ../manage/webhook/add.rst:78 +msgid "_`HTTP Basic Authentication Password`" +msgstr "" + +#: ../manage/webhook/add.rst:92 +msgid "Pre-defined Webhook" +msgstr "" + +#: ../manage/webhook/add.rst:81 +msgid "This field is only available for pre-defined webhooks!" +msgstr "" + +#: ../manage/webhook/add.rst:83 +msgid "" +"This field is always disabled in the UI and serves only as a reference to a " +"pre-defined webhook. It is not possible to change it for existing webhooks." +msgstr "" + +#: ../manage/webhook/add.rst:87 +msgid "" +"Depending on the pre-defined webhook type, additional fields may be rendered " +"below this one. They can be used for additional customization of the webhook " +"behavior." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Additional pre-defined webhook fields" +msgstr "" + +#: ../manage/webhook/add.rst:114 +msgid "_`Custom Payload`" +msgstr "" + +#: ../manage/webhook/add.rst:95 +msgid "" +"Defaults to off - webhook will always send :ref:`webhook-payload-default` to " +"the target endpoint." +msgstr "" + +#: ../manage/webhook/add.rst:98 +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." +msgstr "" + +#: ../manage/webhook/add.rst:0 +msgid "Custom payload code editor" +msgstr "" + +#: ../manage/webhook/add.rst:108 +msgid "" +"Custom payload must be valid JSON syntax! Code editor will inform you via " +"automated hints if there is an issue with the code. Also, it will not be " +"possible to save an invalid JSON structure." +msgstr "" + +#: ../manage/webhook/add.rst:113 +msgid "" +"Pre-defined webhooks will always provide an initial custom payload, specific " +"for the associated service." +msgstr "" + +#: ../manage/webhook/add.rst:117 +msgid "" +"If required you can leave useful information for other Zammad admins to " +"understand the webhook in question better." +msgstr "" + +#: ../manage/webhook/add.rst:121 +msgid "" +"If set to ``inactive`` you can no longer select the webhook within trigger " +"or scheduler actions." +msgstr "" + +#: ../manage/webhook/add.rst:126 +msgid "" +"Inactive webhooks used by triggers or schedulers will not be fired. If " +"triggers or schedulers have other actions configured as well they will still " +"be executed." +msgstr "" + +#: ../manage/webhook/examples.rst:2 +msgid "Webhook Examples" +msgstr "" + +#: ../manage/webhook/examples.rst:18 +msgid ":doc:`examples/mattermost-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:14 +msgid "Use a Mattermost Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/mattermost-notifications.rst:100 +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Sample Mattermost Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:25 +msgid ":doc:`examples/microsoft-teams-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:21 +msgid "Use a Microsoft Teams Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Sample Teams Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:32 +msgid ":doc:`examples/rocket-chat-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:28 +msgid "Use a Rocket Chat Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:96 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Sample Rocket Chat Channel Notification" +msgstr "" + +#: ../manage/webhook/examples.rst:38 +msgid ":doc:`examples/slack-notifications`" +msgstr "" + +#: ../manage/webhook/examples.rst:35 +msgid "Use a Slack Channel to receive your Zammad Notifications." +msgstr "" + +#: ../manage/webhook/examples.rst:0 +#: ../manage/webhook/examples/slack-notifications.rst:108 +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Sample Slack Channel Notification" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:2 +msgid "Generic Notifications Trigger" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:4 +msgid "" +"For posting a notification to an external service, you can use a dedicated :" +"doc:`Trigger `. Here we will outline steps needed to create " +"a Trigger which will fire a webhook under certain conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:8 +msgid "" +"Go to Trigger management screen, and click on the green **New Trigger** " +"button." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:10 +msgid "First, provide a suitable **Name** for the trigger." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Trigger Activator and Action Execution Mode" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:15 +msgid "Next, choose a suitable activator type under **Activated by** field:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:75 ../system/sessions.rst:61 +msgid "Action" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:18 +msgid "" +"This will execute the trigger on a specific action, e.g. user creating or " +"updating a ticket, an email coming in." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:21 +msgid "" +"If you choose **Action** activator, you can set one of the two options for " +"**Action execution**, in order to influence how it evaluates configured " +"conditions:" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:28 +msgid "Selective" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:26 +msgid "" +"This will check if any property used as a condition attribute was updated by " +"the action. If the action behind the trigger was one other than update, it " +"will simply check if the conditions match." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:32 +msgid "Always" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:31 +msgid "" +"This will check if the current state of the ticket matches configured " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:39 +msgid "Time event" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:35 +msgid "" +"This will execute the trigger at a specific time, e.g. when a ticket pending " +"time is reached." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:38 +msgid "" +"**Time event** activator simply checks if conditions match. This is the same " +"behavior as **Always** execution mode for **Action** activator." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:41 +msgid "" +"For **Conditions for affected objects**, you may configure any of the " +"following recipes, or their combination." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:46 +msgid "Ticket Created ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:45 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *created*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:50 +msgid "Ticket Updated ``Action activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:49 +msgid "" +"Select ticket **Action** attribute, leave the operator on *is* and set the " +"value to *updated*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:54 +msgid "Ticket Pending Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:53 +msgid "" +"Select ticket **Pending till** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:58 +msgid "Ticket Escalation Time Reached ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:57 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:62 +msgid "Ticket Escalation Time Reached Warning ``Time event activator only``" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:61 +msgid "" +"Select ticket **Escalation at** attribute and set the operator to *has " +"reached warning*." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:64 +msgid "" +"For complex conditions, you can switch on **Expert Mode** under the " +"conditions field. This will allow you to change the condition group " +"operators to *Match any (OR)*. See :doc:`/misc/object-conditions/expert-" +"mode` for more information." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:68 +msgid "" +"Next, under **Execute changes on objects**, change the initial attribute to " +"*Notification > Webhook* and select your notifications webhook from the list." +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:None +msgid "Configuring Trigger for firing of Webhook" +msgstr "" + +#: ../manage/webhook/examples/generic-notifications-trigger.rst:76 +msgid "Finally, click on **Submit** to save the trigger." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:2 +msgid "Mattermost Notifications" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Mattermost channel." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Mattermost Channel" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:10 +msgid "" +"In your Mattermost top-left corner product menu, choose **Integrations**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Integrations menu item in Mattermost" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:16 +msgid "Click on **Incoming Webhooks** integration button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhooks in Mattermost Integratons" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:22 +msgid "Click on **Add Incoming Webhook** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Add Incoming Webhook button" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:28 +msgid "" +"Provide an appropriate **Title** and **Description** for the incoming " +"webhook, and choose a target **Channel** for the notification messages." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:31 +msgid "" +"Optionally, you may choose to check **Lock to this channel** to limit " +"notifications to a single Mattermost channel. If unset, it will be possible " +"to configure the target channel from Zammad side as well." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Incoming Webhook Setup" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:39 +msgid "Click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:41 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36 +msgid "" +"Once created, make sure to copy *the webhook endpoint URL* to clipboard and " +"save it for later. You can do this in one click via the button shown right " +"next to the field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Copying Incoming Webhook URL" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:49 +msgid "Finally, close the incoming webhook setup by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:52 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:47 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:48 +#: ../manage/webhook/examples/slack-notifications.rst:67 +msgid "Step 2 - Add a Pre-defined Webhook in Zammad" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:54 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:49 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:50 +#: ../manage/webhook/examples/slack-notifications.rst:69 +msgid "" +"Go to :doc:`Webhook ` management screen in your Zammad " +"instance and click on the arrow next to the green button in the upper right " +"corner. Choose **Pre-defined Webhook** from the dropdown menu." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:63 +msgid "" +"In the subsequent modal dialog, select **Mattermost Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "New Mattermost Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:71 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:66 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:67 +#: ../manage/webhook/examples/slack-notifications.rst:86 +msgid "Click **Next**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:73 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Mattermost into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:76 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications. Default value is *zammad*." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:79 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Mattermost " +"incoming webhook." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Configuring Mattermost Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:88 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:76 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:84 +#: ../manage/webhook/examples/slack-notifications.rst:96 +msgid "Finally, click on **Submit**." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:91 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:79 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:87 +#: ../manage/webhook/examples/slack-notifications.rst:99 +msgid "Step 3 - Configuring a Trigger for firing of the Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:93 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Mattermost channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:97 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:85 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:93 +#: ../manage/webhook/examples/slack-notifications.rst:105 +msgid "Once the trigger is in place, your webhook is ready for use!" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:102 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Mattermost Channel. " +"The notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will " +"also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:118 +msgid "Removing Article Content from the Mattermost Notification" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:120 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:108 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:116 +#: ../manage/webhook/examples/slack-notifications.rst:129 +msgid "" +"If you are concerned about leaking sensitive article content via " +"notifications, there is a way to remove them by further customizing the " +"webhook payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:123 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:111 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:119 +#: ../manage/webhook/examples/slack-notifications.rst:132 +msgid "" +"Find your webhook in the list on the management screen and click on it to " +"edit it." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:126 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:114 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:122 +#: ../manage/webhook/examples/slack-notifications.rst:135 +msgid "" +"Switch on **Custom Payload** and the code editor below will be shown, pre-" +"populated with the default payload." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:129 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:125 +#: ../manage/webhook/examples/slack-notifications.rst:138 +msgid "" +"Next, identify the line starting with ``\"text\": \"...`` block in the JSON " +"structure." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:137 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:133 +#: ../manage/webhook/examples/slack-notifications.rst:146 +msgid "" +"Scroll horizontally to the end of the line and select ``\\n\\n#{notification." +"body}`` part near the end. Be sure not to include the end double quote with " +"comma (``\",``) in the rest of the line, since the new payload must remain a " +"valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload with Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:147 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:143 +#: ../manage/webhook/examples/slack-notifications.rst:156 +msgid "Then, simply delete the selected code." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:None +msgid "Custom Payload w/o Article Content for Mattermost Webhook" +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:154 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:150 +#: ../manage/webhook/examples/slack-notifications.rst:163 +msgid "Finally, click on **Submit** to save your webhook changes." +msgstr "" + +#: ../manage/webhook/examples/mattermost-notifications.rst:156 +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:135 +#: ../manage/webhook/examples/rocket-chat-notifications.rst:152 +#: ../manage/webhook/examples/slack-notifications.rst:165 +msgid "" +"On the next invocation of the webhook, the notification will not include " +"content of the last article." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:2 +msgid "Microsoft Teams Notifications" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Microsoft Teams channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:8 +msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:10 +msgid "" +"In your target Teams Channel, click on the overflow menu in the upper right " +"corner and choose **Connectors**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Connectors menu item in a Teams Channel" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:17 +msgid "" +"Find a connector named **Incoming Webhook** in the list and click on " +"**Configure** button next to it." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Incoming Webhook in the Connectors list" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:24 +msgid "" +"Provide an appropriate name for the incoming webhook connector, keeping in " +"mind this will be used as the name for all of the notification messages in " +"the channel." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:28 +msgid "Optionally, provide a custom image which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:34 +msgid "Click on **Create** and be patient." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Copying Incoming Webhook Connector URL" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:44 +msgid "Finally, close the connector configuration by clicking **Done**." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:58 +msgid "" +"In the subsequent modal dialog, select **Microsoft Teams Notifications** as " +"the pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "New Microsoft Teams Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:68 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Microsoft Teams " +"into **Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Configuring Microsoft Teams Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:81 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Microsoft Teams channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:90 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Teams Channel. The " +"notification will contain the link to the ticket, updated data and :ref:" +"`content of the last article `. It will also be " +"`color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:106 +msgid "Removing Article Content from the Teams Notification" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:117 +msgid "" +"Next, identify ``{ \"text\": \"#{notification.body}\" }`` block in the JSON " +"structure and select it. Be sure to include the comma (``,``) in the " +"preceding line, since the new payload must remain a valid JSON value." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload with Article Content" +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:126 +msgid "Then, simply delete the selected code block." +msgstr "" + +#: ../manage/webhook/examples/microsoft-teams-notifications.rst:None +msgid "Custom Payload w/o Article Content" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:2 +msgid "Rocket Chat Notifications" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Rocket Chat channel." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:8 +msgid "" +"Step 1 - Setup Incoming Webhooks Integration for your Rocket Chat Channel" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:10 +msgid "In your Rocket Chat overflow administration menu, choose **Workspace**." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Workspace menu item in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:16 +msgid "" +"In the left sidebar choose **Integrations** and then click on the **New** " +"button in the upper right corner." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Integration button in Rocket Chat" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:23 +msgid "First, turn on the **Enabled** switch on top." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:25 +msgid "" +"Provide an appropriate **Name** for the incoming integration and enter the " +"target channel into **Post to Channel** field, in ``#channel-name`` format." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:28 +msgid "" +"Enter the Rocket Chat username into **Post as** field, without the ``@`` " +"prefix. Note that the username must already exist." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Incoming Integration Setup" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:35 +msgid "Scroll to the end of the form and click on **Save** button." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:37 +msgid "" +"Once successfully saved, make sure to copy *the webhook endpoint URL* to " +"clipboard and save it for later. You can do this in one click via the button " +"shown inside the field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Copying Incoming Integration URL" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:45 +msgid "" +"Finally, close the Administration panel by clicking on ``X`` on the left " +"side." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:59 +msgid "" +"In the subsequent modal dialog, select **Rocket Chat Notifications** as the " +"pre-defined webhook." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "New Rocket Chat Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:69 +msgid "" +"In the new dialog, paste *the webhook endpoint URL* from Rocket Chat into " +"**Endpoint** field." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:72 +msgid "" +"Optionally, you can set **Messaging Username** which will be used to post " +"the Zammad notifications." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:75 +msgid "" +"Optionally, you can also set **Messaging Channel**, if you would like to " +"post to a different target channel than configured in the Rocket Chat " +"incoming integration." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Configuring Rocket Chat Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:89 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Rocket Chat channel under " +"certain conditions." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:98 +msgid "" +"From now on, whenever a ticket is created or updated in your Zammad system, " +"a suitable notification will be posted in the configured Rocket Chat " +"Channel. The notification will contain the link to the ticket, updated data " +"and :ref:`content of the last article `. " +"It will also be `color coded`_ according to its latest state." +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:114 +msgid "Removing Article Content from the Rocket Chat Notification" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload with Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/rocket-chat-notifications.rst:None +msgid "Custom Payload w/o Article Content for Rocket Chat Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:2 +msgid "Slack Notifications" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:4 +msgid "" +"Follow the steps below to configure a webhook for receiving Zammad " +"notifications in a Slack channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:8 +msgid "Step 1 - Setup Incoming WebHooks App in your Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:10 +msgid "" +"In your target Slack Channel, click on the channel name in the upper left " +"part of the screen to get to channel details." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Accessing Channel Details in a Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:17 +msgid "Switch to **Integrations** tab and click on **Add an App** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding an App to Slack Channel" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:23 +msgid "" +"On the next screen, search for an app called *Incoming WebHooks* and click " +"on **Install** button next to it." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Searching for Creating Incoming Webhook Connector" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:30 +msgid "" +"You will be redirected to the Slack App Directory website, where you can add " +"the app." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:33 +msgid "Click on **Add to Slack** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Adding Incoming WebHooks App to Slack" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:40 +msgid "" +"On the next screen, in **Post to Channel** choose your channel from the list " +"and click on **Add Incoming WebHooks integration** button." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Post to Channel Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:48 +msgid "In the final screen, scroll down to **Integration Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:50 +msgid "" +"Make sure to copy **Webhook URL** to clipboard and save it for later. You " +"can do this in one click via the **Copy URL** link shown right below the " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:53 +msgid "" +"You can also fill **Customize Name** field with an appropriate username for " +"the incoming webhooks integration, as this will be used for all of the " +"notification messages in the channel." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:57 +msgid "" +"Optionally, you can **Customize Icon** which will be used as the avatar." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Integration Settings of Incoming WebHooks App" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:64 +msgid "Finally, save your app configuration by clicking **Save Settings**." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:78 +msgid "" +"In the subsequent modal dialog, select **Slack Notifications** as the pre-" +"defined webhook." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "New Slack Notifications Pre-defined Webhook modal" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:88 +msgid "" +"In the new dialog, paste **Webhook URL** from Slack App into **Endpoint** " +"field." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Configuring Slack Webhook endpoint" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:101 +msgid "" +"As a last step, you need to create a :doc:`Trigger ` for posting a notification to the Slack channel under certain " +"conditions." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:110 +msgid "" +"From now on, whenever a ticket is escalated or has reached escalation " +"warning in your Zammad system, a suitable notification will be posted in the " +"configured Slack Channel. The notification will contain the link to the " +"ticket, escalation information and :ref:`content of the last article `. It will also be `color coded`_ according to its " +"latest state." +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:127 +msgid "Removing Article Content from the Slack Notification" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload with Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/examples/slack-notifications.rst:None +msgid "Custom Payload w/o Article Content for Slack Webhook" +msgstr "" + +#: ../manage/webhook/log.rst:2 +msgid "Webhook Logs" +msgstr "" + +#: ../manage/webhook/log.rst:4 +msgid "" +"Zammad provides a history of your recent webhooks. You can find them below " +"**Recent logs**." +msgstr "" + +#: ../manage/webhook/log.rst:0 +msgid "Webhook logs showing possible issues with third party communication" +msgstr "" + +#: ../manage/webhook/log.rst:12 +msgid "" +"If you need more details you can click on the request link in question. " +"Zammad will provide a modal with the following information:" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Direction" +msgstr "" + +#: ../manage/webhook/log.rst:16 +msgid "Always ``out``." +msgstr "" + +#: ../manage/webhook/log.rst:19 +msgid "The URL Zammad sent the request to." +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Method" +msgstr "" + +#: ../manage/webhook/log.rst:22 +msgid "Always ``POST``." +msgstr "" + +#: ../manage/webhook/log.rst:26 +msgid "Status" +msgstr "" + +#: ../manage/webhook/log.rst:25 +msgid "" +"Contains the HTTP status code the remote server replied with. Should be " +"``2xx`` if successful." +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Request" +msgstr "" + +#: ../manage/webhook/log.rst:29 +msgid "Contains the request Zammad sent (HTTP header and payload)" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Response" +msgstr "" + +#: ../manage/webhook/log.rst:32 +msgid "Contains the remotes response header." +msgstr "" + +#: ../manage/webhook/log.rst:35 +msgid "Date and time the request was sent." +msgstr "" + +#: ../manage/webhook/payload.rst:2 +msgid "Webhook Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:4 +msgid "**🤓 A more personal payload...**" +msgstr "" + +#: ../manage/webhook/payload.rst:6 +msgid "" +"Your Zammad instance also provides an example for the default payload. This " +"payload *does fit your installation* and includes your custom objects!" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "Example Payload provides a payload for the particular instance" +msgstr "" + +#: ../manage/webhook/payload.rst:15 +msgid "Request headers" +msgstr "" + +#: ../manage/webhook/payload.rst:17 +msgid "Zammad sends the following headers in each webhook POST request:" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``User-Agent``" +msgstr "" + +#: ../manage/webhook/payload.rst:19 +msgid "``\"Zammad User Agent\"``" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Trigger``" +msgstr "" + +#: ../manage/webhook/payload.rst:20 +msgid "The name of the originating trigger" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Zammad-Delivery``" +msgstr "" + +#: ../manage/webhook/payload.rst:21 +msgid "A unique, random ID string" +msgstr "" + +#: ../manage/webhook/payload.rst:0 +msgid "``X-Hub-Signature``" +msgstr "" + +#: ../manage/webhook/payload.rst:22 +msgid "" +"The SHA-1 hash of your HMAC-SHA1 signature token (assuming you provided one " +"when creating your trigger)" +msgstr "" + +#: ../manage/webhook/payload.rst:28 +msgid "Default JSON Payload" +msgstr "" + +#: ../manage/webhook/payload.rst:30 +msgid "" +"When the webhook payload is not customized, requests will include default " +"payload depending on the webhook type." +msgstr "" + +#: ../manage/webhook/payload.rst:34 +msgid "Regular Webhooks (example)" +msgstr "" + +#: ../manage/webhook/payload.rst:336 +msgid "" +"For better readability, all empty and ``null`` values have been omitted from " +"the sample payload above. That means the webhooks you receive *will include " +"additional fields not shown here*." +msgstr "" + +#: ../manage/webhook/payload.rst:340 +msgid "" +"Webhooks will also include fields for any relevant :doc:`custom objects ` defined in your system." +msgstr "" + +#: ../manage/webhook/payload.rst:343 +msgid "" +"Attachments are *not included*; links to attachments *are* (authentication " +"required)." +msgstr "" + +#: ../manage/webhook/payload.rst:346 +msgid "Linked tickets are *not included*." +msgstr "" + +#: ../manage/webhook/payload.rst:348 +msgid "None of the following **user attributes** are included:" +msgstr "" + +#: ../manage/webhook/payload.rst:350 +msgid "``last_login``" +msgstr "" + +#: ../manage/webhook/payload.rst:351 +msgid "``login_failed``" +msgstr "" + +#: ../manage/webhook/payload.rst:352 +msgid "``password``" +msgstr "" + +#: ../manage/webhook/payload.rst:353 +msgid "``preferences``" +msgstr "" + +#: ../manage/webhook/payload.rst:354 +msgid "``group_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:355 +msgid "``groups``" +msgstr "" + +#: ../manage/webhook/payload.rst:356 +msgid "``authorization_ids``" +msgstr "" + +#: ../manage/webhook/payload.rst:357 +msgid "``authorizations``" +msgstr "" + +#: ../manage/webhook/payload.rst:360 +msgid "Pre-defined Webhooks" +msgstr "" + +#: ../manage/webhook/payload.rst:362 +msgid "" +"Each pre-defined webhook template provides a special payload designed for a " +"particular service. See :doc:`/manage/webhook/examples` for more information." +msgstr "" + +#: ../misc/composer.rst:2 +msgid "Composer Settings" +msgstr "" + +#: ../misc/composer.rst:7 +msgid "" +"Use the Composer Settings to change the behavior of the new message editor." +msgstr "" + +#: ../misc/composer.rst:11 +msgid "" +"These settings **apply on all tickets and to all users across the entire " +"system**." +msgstr "" + +#: ../misc/composer.rst:19 +msgid "Note - default visibility (default: ``internal``)" +msgstr "" + +#: ../misc/composer.rst:15 +msgid "" +"This setting decides what the default visbility of note articles is. This " +"affects **only** notes (default article on ticket answering). The visibility " +"of phone- and email article notes is not affected." +msgstr "" + +#: ../misc/composer.rst:29 +msgid "Article - visibility confirmation dialog" +msgstr "" + +#: ../misc/composer.rst:22 +msgid "" +"This setting allows administrators to enforce a confirmation dialog to " +"agents when they're trying to change the article visibility from internal to " +"public." +msgstr "" + +#: ../misc/composer.rst:26 +msgid "" +"This setting affects all article types within UI, no matter if the article " +"exists already or it's still a writing draft." +msgstr "" + +#: ../misc/composer.rst:41 +msgid "Email - subject field (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:32 +msgid "" +"When setting this option to ``yes``, Zammad will also display the subject " +"field when answering via email articles. It doesn't matter if you click on " +"``reply`` or switch to email article manually." +msgstr "" + +#: ../misc/composer.rst:38 +msgid "" +"Please note that if set to ``no``, Zammad will automatically use the tickets " +"title as subject!" +msgstr "" + +#: ../misc/composer.rst:41 +msgid "" +"The subject can differ between title and mail subject if choosing ``yes``." +msgstr "" + +#: ../misc/composer.rst:51 +msgid "Email - full quote (default: ``no``)" +msgstr "" + +#: ../misc/composer.rst:44 +msgid "" +"Setting this option to ``yes`` will always add the content of the answered " +"article as quotation below your signature." +msgstr "" + +#: ../misc/composer.rst:49 +msgid "" +"This does not affect the \"mark and quote\" functionality, if you mark a " +"text with this setting enabled, we'll use the marked text as quote instead." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Email - quote header (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:54 +msgid "" +"If you don't want Zammad to add the date, time and name or the article " +"you're quoting, set this to ``no``." +msgstr "" + +#: ../misc/composer.rst:57 +msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``" +msgstr "" + +#: ../misc/composer.rst:61 +msgid "Twitter - tweet initials (default: ``yes``)" +msgstr "" + +#: ../misc/composer.rst:60 +msgid "" +"When set to yes, this will add ``/CM`` (first character of first- and last " +"name) to the bottom of every tweet answer you create. This only affects " +"tickets that come from the Twitter Channel." +msgstr "" + +#: ../misc/object-conditions/basics.rst:2 +msgid "Basic object conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:4 +msgid "" +"While this page mainly shows screenshots within Trigger configuration, these " +"information do apply for all supported configurations." +msgstr "" + +#: ../misc/object-conditions/basics.rst:7 +msgid "" +"You will learn what condition options are available by type and how to use " +"them. If you need configuration samples, please refer to the documentation " +"page of the function (e.g. Triggers) you want to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:14 +msgid "Please note that ticket conditions do not support the following:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:16 +msgid "regular expressions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:17 +msgid "case sensitive string conditions" +msgstr "" + +#: ../misc/object-conditions/basics.rst:18 +msgid "" +"Basic conditions do not support the same attribute to be selected more than " +"once" +msgstr "" + +#: ../misc/object-conditions/basics.rst:23 +msgid "" +"The *has changed* condition only is available for ticket attributes and does " +"not affect:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:26 +msgid "ticket articles attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:27 +msgid "organization attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:28 +msgid "user attribtues" +msgstr "" + +#: ../misc/object-conditions/basics.rst:29 +msgid "group attributes" +msgstr "" + +#: ../misc/object-conditions/basics.rst:32 +msgid "How they work" +msgstr "" + +#: ../misc/object-conditions/basics.rst:34 +msgid "" +"Ticket conditions allow you to granulary define a set of attributes and " +"ticket situations to then do certain operations based on these conditions." +msgstr "" + +#: ../misc/object-conditions/basics.rst:37 +msgid "" +"When using the basic mode of conditions, Zammad will match all conditions as " +"*AND* clause. This means that all configured conditions have to fit, if one " +"condition does not, the whole condition set won't fit." +msgstr "" + +#: ../misc/object-conditions/basics.rst:41 +msgid "" +"If you want to use *AND / OR* conditions to cover even more complex " +"conditions, see :doc:`expert-mode`." +msgstr "" + +#: ../misc/object-conditions/basics.rst:45 +msgid "Object types and clauses" +msgstr "" + +#: ../misc/object-conditions/basics.rst:47 +msgid "" +"Zammad offers many different :doc:`object ` (attribute) " +"types which offer various options for matching your conditions. This doesn't " +"just apply to default objects Zammad comes with but also those that you add " +"yourself." +msgstr "" + +#: ../misc/object-conditions/basics.rst:52 +msgid "Special fields" +msgstr "" + +#: ../misc/object-conditions/basics.rst:54 +msgid "" +"Some options or fields are not exactly attributes but functions Zammad " +"offers for your convenience." +msgstr "" + +#: ../misc/object-conditions/basics.rst:96 +msgid "Action *(Scope: Ticket, Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:58 +msgid "This field is only available for Trigger conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is* or *is not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:67 +#: ../misc/object-conditions/basics.rst:111 +#: ../misc/object-conditions/basics.rst:139 +#: ../misc/object-conditions/basics.rst:176 +#: ../misc/object-conditions/basics.rst:227 +#: ../misc/object-conditions/basics.rst:252 +#: ../misc/object-conditions/basics.rst:537 +#: ../misc/object-conditions/basics.rst:590 +msgid "Offered values (multiple choice):" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "created" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "updated" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket has been updated with an article*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "merged into" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The source ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "received merge" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The destination ticket of a ticket merge*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "How was the ticket article in question touched?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:89 +msgid "Available value:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The ticket article has been created*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:124 +msgid "Customer *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:101 +msgid "" +"This field only affects the ticket customer which is set during ticket " +"creation and can be changed manually by an agent." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket customer is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +#: ../misc/object-conditions/basics.rst:359 +#: ../misc/object-conditions/basics.rst:365 +msgid "Available matching: *is*, *is not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the user that caused the trigger run. If your agent or customer " +"updates the ticket, this will be the user. If this was not a human " +"interaction, Zammad will use the system user. This may have unexpected " +"results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific user" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more customers*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "not set (not defined)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:152 +msgid "Organization *(Scope: Ticket, Customer)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:129 +msgid "" +"This field only affects the ticket organization which is set during ticket " +"creation and depends on the ticket customers organization." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket organization is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "current user organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*This is the users organization that caused the trigger run. If your agent " +"or customer updates the ticket, this will be the organization. If this was " +"not a human interaction, Zammad will use no organization. This may have " +"unexpected results!*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "specific organization" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more organizations*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:166 +msgid "Group *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket group is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:162 +msgid "Offers all configured and active groups in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:189 +msgid "Owner *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket owner is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Select one or more owners*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "State *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:194 +msgid "" +"Zammad behaves inconsistent in between certain ticket condition dialogues - " +"if you can see ticket states only in parts of the admin menu and not in the " +"front-end, your state *is not visible*." +msgstr "" + +#: ../misc/object-conditions/basics.rst:198 +msgid "`The system user documentation has you covered`_." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket state is affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:207 +msgid "Offers all configured and *visible* ticket states in Zammad." +msgstr "" + +#: ../misc/object-conditions/basics.rst:240 +msgid "Tags *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:217 +msgid "Additional tags can be present in the ticket without issues." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket tags are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Available matching: *contains all*, *contains one*, *contains all not* or " +"*contains one not*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains all not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given tags are not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "contains one not" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given tags is not present on the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:264 +msgid "Subscribe *(Scope: Ticket)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:243 +msgid "This affects ticket subscriptions / mentions by and for agents." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What ticket subscribers (`notifications`_) are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*This is the user that caused the trigger run. Only can affect agents.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Affects one or more specific users that have subscribed to the ticket.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:285 +msgid "Type *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:267 +msgid "**If you're unsure what article type you're looking for...**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:269 +msgid "Click on a message to see detailed information about it." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Message details view" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles type (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:281 +msgid "Offers all available article types of your instance (e.g. *email*)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:303 +msgid "Visibility *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What's the articles visibility (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:298 +msgid "" +"Allows you to check if the article in question is either internal or public." +msgstr "" + +#: ../misc/object-conditions/basics.rst:317 +msgid "Sender *(Scope: Ticket article)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What user role does the sender of the article have (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:313 +msgid "Determine the sender of the message: System, Agent or Customer." +msgstr "" + +#: ../misc/object-conditions/basics.rst:337 +msgid "Calendar *(Scope: Execution time)*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:320 +msgid "This field is only available for Trigger and Scheduler conditions!" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Was the ticket touched within the calendar defined business time (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching: *is in working time* or *is not in working time*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:330 +msgid "" +"Allows selection of a pre-defined :doc:`calendars ` to " +"check whether the defined business hours are met. This allows time based " +"events like out of business hours responses." +msgstr "" + +#: ../misc/object-conditions/basics.rst:340 +msgid "Text field (input)" +msgstr "" + +#: ../misc/object-conditions/basics.rst:344 +msgid "" +"The configured \"Type\" of input fields as no impact on the available " +"options." +msgstr "" + +#: ../misc/object-conditions/basics.rst:346 +msgid "Check if any field of type text contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:347 +#: ../misc/object-conditions/basics.rst:353 +msgid "Available matching: *contains*, *contains not* or *has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:350 ../system/objects/types.rst:113 +msgid "Textarea field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:352 +msgid "" +"Check if any field of type textarea contains a specific string (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:356 ../system/objects/types.rst:16 +msgid "Boolean field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:358 +msgid "Check if any field of type boolean is true (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:362 ../system/objects/types.rst:57 +msgid "Integer field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:364 +msgid "Check if any field of type integer has a specific value (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:368 ../system/objects/types.rst:26 +msgid "Date field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Check if the given date is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Available matching:" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:1 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:2 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (absolute)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:3 +#: ../misc/object-conditions/basics.rst:0 +msgid "*before (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:4 +#: ../misc/object-conditions/basics.rst:0 +msgid "*after (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:5 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within next (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:6 +#: ../misc/object-conditions/basics.rst:0 +msgid "*within last (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:7 +#: ../misc/object-conditions/basics.rst:0 +msgid "*till (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:8 +#: ../misc/object-conditions/basics.rst:0 +msgid "*from (relative)*" +msgstr "" + +#: ../misc/object-conditions/datetime-conditions.include.rst:9 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has changed*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:379 +#: ../misc/object-conditions/basics.rst:450 +msgid "Offered values and options:" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is before the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date field's value is after the configured date, the condition will " +"be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date " +"minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*You can choose from Minute(s), Hour(s), Day(s), Week(s), Month(s) and " +"Year(s).*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is in between the current date " +"and the current date plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is before the current date plus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date field's value if the value is after the current date minus " +"the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The field has been changed during a ticket update.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:424 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you." +msgstr "" + +#: ../misc/object-conditions/basics.rst:430 +msgid "Date & Time field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:434 +msgid "" +"An example for this field type are all default fields handling updated at, " +"created at and closed at timings." +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"Check if the given date & time is past or relatively past a specific period?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:445 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:446 +#: ../misc/object-conditions/basics.rst:0 +msgid "*has reached warning*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is before the configured date and time, " +"the condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*If the date & time field's value is after the configured date and time, the " +"condition will be met.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is in between the " +"current time and the current time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is before the current " +"date and time plus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"*Matches the date & time field's value if the value is after the current " +"date and time minus the selected time period.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Pending time and Escalation " +"time in Trigger conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field was reached*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "" +"**This option is only available for Ticket's Escalation time in Trigger " +"conditions!**" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*The time set in this field will be reached in less than 15 minutes*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:503 +msgid "" +"To help you understand the time conditions of Zammad better, below diagram " +"might also be helpful to you. Below is a carbon copy of the date variant and " +"applies exactly the same just you having hours and minutes on top to use." +msgstr "" + +#: ../misc/object-conditions/basics.rst:510 ../system/objects/types.rst:83 +msgid "Single selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "Checks selected field values to match actual attribute value (or not)." +msgstr "" + +#: ../misc/object-conditions/basics.rst:519 +#: ../misc/object-conditions/basics.rst:567 +msgid "" +"Allows you to select one or more values of the attribute in question. " +"Selecting more than one value in the condition will act like an \"OR\" " +"clause." +msgstr "" + +#: ../misc/object-conditions/basics.rst:527 ../system/objects/types.rst:70 +msgid "Multiple selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "What field's values are affected (or not)?" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if all given field values are not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:0 +msgid "*Matches if one specific given field value is not selected.*" +msgstr "" + +#: ../misc/object-conditions/basics.rst:553 ../system/objects/types.rst:145 +msgid "Single tree selection field" +msgstr "" + +#: ../misc/object-conditions/basics.rst:557 +#: ../misc/object-conditions/basics.rst:579 +msgid "" +"This attribute type technically allows several layers of values. You cannot " +"match a parent layer to match all of it's childs." +msgstr "" + +#: ../misc/object-conditions/basics.rst:575 ../system/objects/types.rst:154 +msgid "Multiple tree selection field" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:2 +msgid "Expert object conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:4 +msgid "**🚧 Hosted environment specific limitation 🚧**" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:6 +msgid "" +"AND / OR (expert mode) for ticket conditions are only available for **Plus** " +"package users." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:9 +msgid "" +"Enabling the *expert mode* within your ticket conditions allows you to use " +"*AND / OR* conditions for any supported method. You can decide which " +"workflow requires this enhanced configuration individually." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:15 +msgid "The option \"Expert mode\" is available since Zammad 5.4." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:17 +msgid "This section expects that you had a look at :doc:`basics` already." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:22 +msgid "Limitation" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:24 +msgid "" +"Zammad offers up to three layers of conditions allowing you to configure " +"very detailed and complex conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:28 +msgid "Switching to Expert mode" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:30 +msgid "" +"You can enable or disable *expert mode* in any supported condition screen. " +"To do so, simply use the *expert mode* button on the lower right below the " +"*conditions for affected objects* area." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing expert mode being enabled in trigger dialog" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:38 +msgid "Logic block conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:40 +msgid "" +"Zammad's condition expert mode allows you to use logic blocks. These blocks " +"enable you to have one or several sets of conditions that have to match your " +"requirement. These blocks allow matching as *and / or* and *no match*." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:47 +msgid "Match all (AND)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:46 +msgid "" +"All conditions in this block will be matched with \"AND\". This requires all " +"conditions to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:51 +msgid "Match any (OR)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:50 +msgid "" +"Any condition in this block will be matched with \"OR\". This requires one " +"condition to be met in order to be matched positive." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:55 +msgid "Match none (NOT)" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:54 +msgid "" +"All conditions in this block will be matched with \"AND\". To be matched " +"positive, no or any condition may match - but not all together." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:57 +msgid "" +"See `Evaluation order`_ to understand how Zammad evaluates triggers in " +"expert mode." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:61 +msgid "Adding conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:63 +msgid "" +"By using the |subclause| icon you can add as many logic blocks as you need. " +"New blocks will be added below the object you're using the |subclause| icon " +"on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:86 +msgid "Icon for adding a new subclause block" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:66 +msgid "" +"The level will be automatically set to a lower level than the object you're " +"using it on." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new logic blocks being added" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:75 +msgid "The same behavior also applies to conditions *within* logic blocks!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:0 +msgid "Screencast showing new conditions being added to logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:83 +msgid "" +"Note that removing condition blocks removes **all blocks and conditions** " +"with it!" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:91 +msgid "Re-arranging conditions and logic blocks" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:93 +msgid "" +"Use ≡ to drag conditions or logic blocks and drop them to the position " +"desired. By using drag and drop, you won't need to remove and re-add " +"conditions." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:98 +msgid "" +"Moving logic blocks will also move any condition and, if applicable, logic " +"blocks that are below it." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:101 +msgid "" +"While you can adjust the order of conditions without any further logic " +"blocks, this won't have any consequences." +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:None +msgid "Screencast showing dragging and dropping conditions" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:108 +msgid "Evaluation order" +msgstr "" + +#: ../misc/object-conditions/expert-mode.rst:110 +msgid "" +"Here's a fairly complex diagram on how Zammad evaluates conditions and their " +"blocks." +msgstr "" + +#: ../misc/object-conditions/index.rst:2 +msgid "Object conditions" +msgstr "" + +#: ../misc/object-conditions/index.rst:4 +msgid "" +"This page will help you to understand Zammad's object conditions better." +msgstr "" + +#: ../misc/object-conditions/index.rst:9 +msgid "" +"Ticket conditions differ from function to function. This affects the " +"availability for certain attribute checks and the expert mode (*AND / OR*). " +"The following functions in Zammad are covered." +msgstr "" + +#: ../misc/object-conditions/index.rst:14 +msgid ":doc:`/manage/slas/index`" +msgstr "" + +#: ../misc/object-conditions/index.rst:17 +msgid ":doc:`/manage/report-profiles`" +msgstr "" + +#: ../misc/object-conditions/index.rst:18 +msgid ":ref:`Automatic ticket assignment `" +msgstr "" + +#: ../misc/object-conditions/index.rst:20 +msgid "" +"All other functions that come with an object condition configuration may not " +"fully support all stated functions." +msgstr "" + +#: ../misc/object-conditions/index.rst:23 +msgid "" +"Some object scopes (e.g. article scope) are not available in all situations, " +"this is due to the nature of each independent functionality. Check the " +"function documentation page affected to learn more." +msgstr "" + +#: ../misc/object-conditions/index.rst:30 +msgid "Getting started" +msgstr "" + +#: ../misc/object-conditions/index.rst:32 +msgid "This guide is split into two major sections which depend on each other." +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid ":doc:`/misc/object-conditions/basics`" +msgstr "" + +#: ../misc/object-conditions/index.rst:35 +msgid "Learn how Zammad's basic conditions work to adapt to your environment." +msgstr "" + +#: ../misc/object-conditions/index.rst:39 +msgid ":doc:`/misc/object-conditions/expert-mode`" +msgstr "" + +#: ../misc/object-conditions/index.rst:38 +msgid "" +"Learn how Zammad's expert mode for conditions allows you to create even more " +"powerful conditions. *AND / OR* conditions have you covered!" +msgstr "" + +#: ../settings/branding.rst:2 +msgid "Branding" +msgstr "" + +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "" + +#: ../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 "" + +#: ../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:24 +msgid "Logo" +msgstr "" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "" + +#: ../settings/branding.rst:20 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Other wise " +"your change will not be saved." +msgstr "" + +#: ../settings/branding.rst:0 +msgid "Screenshot highlighting the submit button of the logo change dialogue" +msgstr "" + +#: ../settings/branding.rst:32 +msgid "Locale" +msgstr "" + +#: ../settings/branding.rst:27 +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:30 +msgid "user preferences (if Zammad can't detect the users locale)" +msgstr "" + +#: ../settings/branding.rst:31 +msgid "CSV output (reporting, time accounting)" +msgstr "" + +#: ../settings/branding.rst:32 ../settings/branding.rst:48 +msgid "notifications" +msgstr "" + +#: ../settings/branding.rst:53 +msgid "Timezone" +msgstr "" + +#: ../settings/branding.rst:35 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:39 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." +msgstr "" + +#: ../settings/branding.rst:44 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "" + +#: ../settings/branding.rst:46 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "" + +#: ../settings/branding.rst:47 +msgid "search indexing (and thus reporting)" +msgstr "" + +#: ../settings/branding.rst:49 +msgid "calendar subscriptions" +msgstr "" + +#: ../settings/branding.rst:50 +msgid "browser printing" +msgstr "" + +#: ../settings/branding.rst:52 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Pretty Date" +msgstr "" + +#: ../settings/branding.rst:56 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" + +#: ../settings/branding.rst:61 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." +msgstr "" + +#: ../settings/branding.rst:95 +msgid "Choose in between the following options:" +msgstr "" + +#: ../settings/branding.rst:77 +msgid "relative" +msgstr "" + +#: ../settings/branding.rst:66 +msgid "" +"This timestamp is the one that changes the most. Over the time it will " +"transition like so:" +msgstr "" + +#: ../settings/branding.rst:69 +msgid "just now" +msgstr "" + +#: ../settings/branding.rst:70 +msgid "5 minutes ago" +msgstr "" + +#: ../settings/branding.rst:71 +msgid "3 days 1 hour ago" +msgstr "" + +#: ../settings/branding.rst:72 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:76 +msgid "" +"Hovering the timestamp helps, you'll always get a clean timestamp if you do." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "absolute" +msgstr "" + +#: ../settings/branding.rst:80 +msgid "" +"This timestamp makes Zammad to always include the week day. For one week " +"after creation the timestamp will not contain the date itself: Thursday " +"18:35." +msgstr "" + +#: ../settings/branding.rst:84 +msgid "After a week it will switch to this: Friday 4. Mar 16:00." +msgstr "" + +#: ../settings/branding.rst:94 +msgid "timestamp" +msgstr "" + +#: ../settings/branding.rst:87 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this would mean: e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." +msgstr "" + +#: ../settings/branding.rst:93 +msgid "" +"This is the most consequent timestamp in Zammad as it does not change it's " +"form and looks the same even over long time periods." +msgstr "" + +#: ../settings/branding.rst:96 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" +msgstr "" + +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" +msgstr "" + +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:10 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +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." +msgstr "" + +#: ../settings/security/base.rst:13 ../settings/security/base.rst:41 +#: ../settings/security/base.rst:68 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" + +#: ../settings/security/base.rst:22 +msgid "**😖 This setting may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:24 +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." +msgstr "" + +#: ../settings/security/base.rst:28 +msgid "" +"User accounts are a direct dependency of tickets and thus technically " +"mandatory." +msgstr "" + +#: ../settings/security/base.rst:32 +msgid "Lost Password" +msgstr "" + +#: ../settings/security/base.rst:36 +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 "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "" + +#: ../settings/security/base.rst:50 ../settings/security/base.rst:83 +msgid "**😖 This function may be confusing**" +msgstr "" + +#: ../settings/security/base.rst:52 +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 "" + +#: ../settings/security/base.rst:59 +msgid "Password Login" +msgstr "" + +#: ../settings/security/base.rst:63 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated." +msgstr "" + +#: ../settings/security/base.rst:66 +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/security/base.rst:79 +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 "" + +#: ../settings/security/base.rst:85 +msgid "" +"Disabling password login on the Zammad login page only takes effect if you " +"enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:91 +msgid "Session Timeout" +msgstr "" + +#: ../settings/security/base.rst:93 +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 "" + +#: ../settings/security/base.rst:98 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." +msgstr "" + +#: ../settings/security/base.rst:101 +msgid "``admin``" +msgstr "" + +#: ../settings/security/base.rst:103 +msgid "``ticket.customer``" +msgstr "" + +#: ../settings/security/base.rst:104 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "" + +#: ../settings/security/base.rst:106 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." +msgstr "" + +#: ../settings/security/base.rst:109 +msgid "**🤓 An example**" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "Let's suppose you configured the following session timeouts" +msgstr "" + +#: ../settings/security/base.rst:112 +msgid "default: 3 weeks" +msgstr "" + +#: ../settings/security/base.rst:113 +msgid "admin: 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:114 +msgid "ticket.agent: 4 weeks" +msgstr "" + +#: ../settings/security/base.rst:115 +msgid "ticket.customer: 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "This results in the following situations" +msgstr "" + +#: ../settings/security/base.rst:118 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:119 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" +msgstr "" + +#: ../settings/security/base.rst:121 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" +msgstr "" + +#: ../settings/security/base.rst:123 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" +msgstr "" + +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." +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 " +"will be addressed in the future by `#1169`_." +msgstr "" + +#: ../settings/security/password.rst:15 +msgid "**💪 Exception for strong passwords 💪**" +msgstr "" + +#: ../settings/security/password.rst:17 +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 "" + +#: ../settings/security/password.rst:22 +msgid "The suggested workflow is either:" +msgstr "" + +#: ../settings/security/password.rst:24 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" + +#: ../settings/security/password.rst:26 +msgid "to require your *user to reset the password* upon first login." +msgstr "" + +#: ../settings/security/password.rst:28 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" + +#: ../settings/security/password.rst:32 +msgid "Maximum failed logins" +msgstr "" + +#: ../settings/security/password.rst:34 +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:39 +msgid "The default value is ``10``." +msgstr "" + +#: ../settings/security/password.rst:43 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "" + +#: ../settings/security/password.rst:45 +msgid ":ref:`user management list `" +msgstr "" + +#: ../settings/security/password.rst:46 +msgid "`console`_" +msgstr "" + +#: ../settings/security/password.rst:47 +msgid "`api`_" +msgstr "" + +#: ../settings/security/password.rst:54 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "" + +#: ../settings/security/password.rst:57 +msgid "2 lower case and 2 upper case characters" +msgstr "" + +#: ../settings/security/password.rst:59 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" + +#: ../settings/security/password.rst:62 ../settings/security/password.rst:87 +msgid "The default value is ``no``." +msgstr "" + +#: ../settings/security/password.rst:66 +msgid "Minimum length" +msgstr "" + +#: ../settings/security/password.rst:68 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" + +#: ../settings/security/password.rst:71 +msgid "The default value is ``6``." +msgstr "" + +#: ../settings/security/password.rst:75 +msgid "Digit required" +msgstr "" + +#: ../settings/security/password.rst:77 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" + +#: ../settings/security/password.rst:79 +msgid "The default value is ``yes``." +msgstr "" + +#: ../settings/security/password.rst:82 +msgid "Special character required" +msgstr "" + +#: ../settings/security/password.rst:84 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" + +#: ../settings/security/third-party.rst:10 +msgid "Login Providers" +msgstr "" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +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 "" + +#: ../settings/security/third-party.rst:24 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" + +#: ../settings/security/third-party.rst:26 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:27 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:31 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"above mentioned authentication providers are enabled in your instance." +msgstr "" + +#: ../settings/security/third-party.rst:37 +msgid "Automatic account link on initial logon" +msgstr "" + +#: ../settings/security/third-party.rst:39 +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 "" + +#: ../settings/security/third-party.rst:44 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this `consult the user documentation`_)." +msgstr "" + +#: ../settings/security/third-party.rst:50 +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 "" + +#: ../settings/security/third-party.rst:54 +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 "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "" + +#: ../settings/security/third-party.rst:64 +msgid "Automatic account linking notification" +msgstr "" + +#: ../settings/security/third-party.rst:68 +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:72 +msgid "" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." +msgstr "" + +#: ../settings/security/third-party.rst:75 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" +msgstr "" + +#: ../settings/security/third-party.rst:89 +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:93 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:95 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:96 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" + +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" +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 "" + +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook app" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook app" +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." +msgstr "" + +#: ../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:49 +#: ../settings/security/third-party/twitter.rst:50 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." +msgstr "" + +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +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 "" + +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub app" +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 "" + +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "" + +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub app" +msgstr "" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +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." +msgstr "" + +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +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 "" + +#: ../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:45 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +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 "" + +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad_host/auth/gitlab/callback\" where " +"zammad_host has to be replaced with your Zammad FQDN" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:18 +msgid "" +"At the moment we need the \"api\" scope. This is caused due a bug in Gitlab: " +"https://gitlab.com/gitlab-org/gitlab-ce/issues/33022" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:22 +msgid "Configure Zammad as Gitlab app" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:24 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:27 +msgid "Please ensure to use ``https://{git_host}/api/v4/`` for site." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:33 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:39 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" +msgstr "" + +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google app" +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." +msgstr "" + +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: ``https://console.cloud.google.com/" +"projectcreate``" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" + +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and savingthe consent screen information, you can change to " +"\"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +msgstr "" + +#: ../settings/security/third-party/google.rst:28 +msgid "" +"Fill in the neceassary information, for restrictions you need the following " +"(replace ``zammad_host`` with your FQDN):" +msgstr "" + +#: ../settings/security/third-party/google.rst:31 +msgid "**Aplication type** ``[x] Web application``" +msgstr "" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "" + +#: ../settings/security/third-party/google.rst:37 +msgid "" +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" +msgstr "" + +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +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 "" + +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" + +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +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 "" + +#: ../settings/security/third-party/microsoft.rst:8 +msgid "**This login function was called \"Office 365\" prior Zammad 5.1.**" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:12 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:32 +#: ../settings/security/third-party/microsoft.rst:57 +msgid "Supported account types:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:24 +msgid "" +"Please note that Zammad only supports these account types (App dependent):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:37 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:35 +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 "" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "Step 1 - Register a Microsoft app for Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:42 +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 "" + +#: ../settings/security/third-party/microsoft.rst:48 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:47 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:51 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:55 +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:62 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:60 +msgid "" +"Select web and provide your callback url. The callback url looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "Contacts" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:75 +msgid "``Contacts.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:77 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:84 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:92 +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 "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:102 +msgid "Step 2 - Add app credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:104 +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 "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "App ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:109 +msgid "This is your *Application (client) ID*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "App secret:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:112 +msgid "This is your *client secret* (value)." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:117 +msgid "App Tenant ID:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:119 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" +msgstr "" + +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:4 +msgid "Connect your SAML identity provider as a single sign-on (SSO) method." +msgstr "" + +#: ../settings/security/third-party/saml.rst:6 +msgid "🤷 **What is SAML?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:8 +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 "" + +#: ../settings/security/third-party/saml.rst:12 +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 "" + +#: ../settings/security/third-party/saml.rst:16 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" + +#: ../settings/security/third-party/saml.rst:27 +msgid "Step 1: Configure Your IdP" +msgstr "" + +#: ../settings/security/third-party/saml.rst:30 +msgid "Add Zammad as a client/app" +msgstr "" + +#: ../settings/security/third-party/saml.rst:32 +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:35 +msgid "🙋 **What if my IdP doesn’t support XML import?**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:37 +msgid "" +"You will have to configure Zammad as a new client/app manually using the " +"above XML metadata file for reference. For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:45 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:50 +msgid "Set up user attribute mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:52 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Email address (``email``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:55 +msgid "Full name (``name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:56 +msgid "Given name (``first_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:57 +msgid "Family name (``last_name``)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:59 +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 "" + +#: ../settings/security/third-party/saml.rst:65 +msgid "Per-IdP Instructions" +msgstr "" + +#: ../settings/security/third-party/saml.rst:101 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:68 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Create > " +"Import** in the Keycloak admin panel." +msgstr "" + +#: ../settings/security/third-party/saml.rst:73 +msgid "" +"**To help Zammad match its own user accounts to Keycloak users,** create a " +"user attribute (or “property”) mapper:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:76 +msgid "" +"**Clients > https://your.zammad.domain/auth/saml/metadata > Mappers > " +"Create**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:79 +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +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 ``emailAddress`` 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 "" + +#: ../settings/security/third-party/saml.rst:98 +msgid "Make sure the **Client ID** matches the **Master SAML Processing URL**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:100 +msgid "You need to enable **Sign assertions**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:104 +msgid "Step 2: Configure Zammad" +msgstr "" + +#: ../settings/security/third-party/saml.rst:106 +msgid "" +"Enable SAML and enter your IdP’s details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML" +msgstr "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Display name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:113 +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 "" + +#: ../settings/security/third-party/saml.rst:116 +msgid "Defaults to ``SAML``." +msgstr "" + +#: ../settings/security/third-party/saml.rst:120 +msgid "IDP SSO Target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:119 +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 "" + +#: ../settings/security/third-party/saml.rst:124 +msgid "IDP Certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:123 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:138 +msgid "IDP Certificate fingerprint" +msgstr "" + +#: ../settings/security/third-party/saml.rst:127 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "" + +#: ../settings/security/third-party/saml.rst:132 +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 "" + +#: ../settings/security/third-party/saml.rst:137 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > RSA > Certificate**." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Name Identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:141 +msgid "" +"This is the unique identifiers field type. Usually should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress`` in any case." +msgstr "" + +#: ../settings/security/third-party/saml.rst:146 +msgid "Zammad expects an email address as unique identifier!" +msgstr "" + +#: ../settings/security/third-party/saml.rst:150 +msgid "Your callback URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:149 +msgid "" +"This URL is needed for your IDP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" + +#: ../settings/security/third-party/saml.rst:152 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." +msgstr "" + +#: ../settings/security/third-party/saml.rst:158 +msgid "Automatic account linking doesn’t work" +msgstr "" + +#: ../settings/security/third-party/saml.rst:159 +msgid "" +"Have you double-checked your IdP’s user attribute mapping configuration?" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +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\"" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:23 +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:29 +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:35 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:39 +msgid "Configure Zammad as Twitter app" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:41 +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:47 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the \"Submit" +"\" button." +msgstr "" + +#: ../settings/system/system-selfhosted.include.rst:1 +msgid "**🚧 Self Hosted only 🚧**" +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 "" + +#: ../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:3 +msgid "This setting is automatically set by the Getting Started wizard." +msgstr "" + +#: ../settings/system/system-base.include.rst:7 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" + +#: ../settings/system/system-base.include.rst:8 +msgid "This setting can have negative affects on being able to login." +msgstr "" + +#: ../settings/system/base.rst:19 +msgid "HTTP type" +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." +msgstr "" + +#: ../settings/system/base.rst:31 +msgid "SystemID" +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." +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 "" + +#: ../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 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" +msgstr "" + +#: ../settings/system/index.rst:16 +msgid "Console based settings 🤓" +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 `hidden settings`_ section." +msgstr "" + +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Proxy Settings" +msgstr "" + +#: ../settings/system/network.rst:9 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:13 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:16 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:19 +msgid "" +"If your proxy server requires authentication, provide the username here." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "Password for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:22 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:25 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:28 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "" + +#: ../settings/system/services.rst:12 +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:11 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``images.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:20 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:15 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"succession." +msgstr "" + +#: ../settings/system/services.rst:18 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:3 +msgid "" +"On premise installations behind restrictive firewalls require ``HTTPS`` " +"access to ``geo.zammad.com``." +msgstr "" + +#: ../settings/system/services.rst:28 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:23 +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:26 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:31 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." +msgstr "" + +#: ../settings/system/services.rst:34 +msgid "Default: ``Geo Location Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:38 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our `Privacy Appendix`_ inside of our System-Administrator-Documentation." +msgstr "" + +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "Storage Mechanism" +msgstr "" + +#: ../settings/system/storage.rst:7 +msgid "" +"This tells Zammad where to store attachments for tickets and knowledge base." +msgstr "" + +#: ../settings/system/storage.rst:9 +msgid "" +"By default we're writing to the ``Database`` - you can switch to " +"``Filesystem`` at any time. If you chose filesystem, your files are written " +"to ``/opt/zammad/storage/``" +msgstr "" + +#: ../settings/system/storage.rst:15 +msgid "" +"We strongly encourage you to use filesystem storage on busy instances. This " +"will greatly improve system performance (de-crease database load and size)." +msgstr "" + +#: ../settings/system/storage.rst:21 +msgid "" +"Moving attachments from Database to Filesystem can be run during production " +"use." +msgstr "" + +#: ../settings/ticket.rst:6 +msgid "" +"Additional settings for the ticket composer interface can be found in the :" +"doc:`/misc/composer`." +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "" + +#: ../settings/ticket.rst:13 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "" + +#: ../settings/ticket.rst:40 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "" + +#: ../settings/ticket.rst:16 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "*Right*" +msgstr "" + +#: ../settings/ticket.rst:19 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "" + +#: ../settings/ticket.rst:22 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "*Left*" +msgstr "" + +#: ../settings/ticket.rst:25 +msgid "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "" + +#: ../settings/ticket.rst:28 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "*None*" +msgstr "" + +#: ../settings/ticket.rst:31 +msgid "This will completely remove ticket references from the subject." +msgstr "" + +#: ../settings/ticket.rst:35 +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 "" + +#: ../settings/ticket.rst:39 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" +msgstr "" + +#: ../settings/ticket.rst:68 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" +msgstr "" + +#: ../settings/ticket.rst:43 +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 "" + +#: ../settings/ticket.rst:54 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." +msgstr "" + +#: ../settings/ticket.rst:48 +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 "" + +#: ../settings/ticket.rst:52 +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 "" + +#: ../settings/ticket.rst:59 +msgid "Use the time of the very last customer article." +msgstr "" + +#: ../settings/ticket.rst:57 +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 "" + +#: ../settings/ticket.rst:66 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "" + +#: ../settings/ticket.rst:67 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "" + +#: ../settings/ticket.rst:74 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:78 +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 "" + +#: ../settings/ticket.rst:82 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "" + +#: ../settings/ticket.rst:90 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:85 +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 "" + +#: ../settings/ticket.rst:90 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "OPTIONS" +msgstr "" + +#: ../settings/ticket.rst:93 +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 "" + +#: ../settings/ticket.rst:102 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:98 +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/ticket.rst:102 +msgid "This will also add another digit to the ticket number." +msgstr "" + +#: ../settings/ticket.rst:119 +msgid "Min. size of Number (default: ``5``)" +msgstr "" + +#: ../settings/ticket.rst:105 +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 "" + +#: ../settings/ticket.rst:109 +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 "" + +#: ../settings/ticket.rst:117 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" +msgstr "" + +#: ../settings/ticket.rst:124 +msgid "Auto-Assignment" +msgstr "" + +#: ../settings/ticket.rst:126 +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 "" + +#: ../settings/ticket.rst:133 +msgid "" +"Auto Assignment only kicks in if the ticket has no owner yet. By default the " +"agent can always reset the ticket owner to ``-`` if needed." +msgstr "" + +#: ../settings/ticket.rst:136 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under within Settings -> Ticket -> Auto assignment." +msgstr "" + +#: ../settings/ticket.rst:139 +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 "" + +#: ../settings/ticket.rst:145 +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." +msgstr "" + +#: ../settings/ticket.rst:150 +msgid "" +"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:154 +msgid "Notifications" +msgstr "" + +#: ../settings/ticket.rst:179 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:157 +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/ticket.rst:162 +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 "" + +#: ../settings/ticket.rst:166 +msgid "**🥵 Potential time-consuming action**" +msgstr "" + +#: ../settings/ticket.rst:168 +msgid "" +"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/ticket.rst:172 +msgid "**Active agents only!**" +msgstr "" + +#: ../settings/ticket.rst:174 +msgid "" +"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/ticket.rst:178 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." +msgstr "" + +#: ../settings/ticket.rst:182 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:224 +msgid "Detect Duplicate Ticket Creation" +msgstr "" + +#: ../settings/ticket.rst:185 +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 "" + +#: ../settings/ticket.rst:192 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:194 +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:199 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:201 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." +msgstr "" + +#: ../settings/ticket.rst:204 +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 "" + +#: ../settings/ticket.rst:207 +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 "" + +#: ../settings/ticket.rst:213 +msgid "**🦺 Safety first!**" +msgstr "" + +#: ../settings/ticket.rst:215 +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 "" + +#: ../settings/ticket.rst:219 +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/ticket.rst:223 +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/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to create complex ticket processes just as (but not " +"limited to):" +msgstr "" + +#: ../system/core-workflows.rst:7 +msgid "show / hide" +msgstr "" + +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "" + +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you're all set to provide exactly those information you really " +"need!" +msgstr "" + +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." +msgstr "" + +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" +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." +msgstr "" + +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are evaluated by priority. If 2 workflows have the same " +"priority by alphabetical order by **name**. Workflows are evaluated in " +"alphabetical order, by **name.**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows works all changes to attributes are " +"checked with the application server – please see :doc:`limitations` for " +"possible issues." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that have an impact and are not self-" +"explanatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:16 +msgid "Object" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:18 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available conditions and actions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:23 +msgid "" +"You will be able to use objects that are in relation to your selection in " +"your conditions." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "This means:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Ticket objects also have access to the ticket customer." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:32 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to reduce workflows." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:37 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:36 +msgid "" +"Once selected your conditions and actions will affect all applicable " +"creation masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:41 +msgid "Edit mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:40 +msgid "" +"Once selected your conditions and actions will affect all applicable edit " +"masks." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:46 +msgid "" +"Zammad decides in between selected and saved conditions. These can be " +"combined wherever needed." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:49 +msgid "**🤓 Combining conditions allows \"OR\"-selections**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:51 +msgid "" +"However, note that each condition type counts as *and* selector and can't " +"overrule the other condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:54 +msgid "Every attribute can be used once per condition type." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:56 +msgid "**⚠ Restrict on role basis if needed ⚠**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:58 +msgid "" +"By default, unless configured in conditions, workflow rules are evaluated " +"for **all roles**. This also affects your customers! 🙀" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "Selected Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:62 +msgid "" +"These conditions only match if they're active in selection. This applies for " +"drafts (active selection) and currently saved values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"These conditions only apply if they're saved within the database regardless " +"of the current value or selection of the field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:71 +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/core-workflows/how-do-they-work.rst:77 +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:81 +msgid "**🚧 Actions are not available for relations**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:83 +msgid "" +"Let's say you're working in ticket context. While you can have customer " +"conditions, you can't adjust objects with actions in that scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:87 +msgid "" +"That's because this wouldn't have any impact on the ticket dialogue. All " +"ticket attributes (state, owner, ...) are available." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:92 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:96 +msgid "Available Operators" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:100 +msgid "The availability of operators depends on the object type and scope." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "**🧐 Actions can cause confusion**" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +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 "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:181 +msgid "api" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:185 +msgid "ui" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "show |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:111 +msgid "Display the field in question. Allows setting of values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:120 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:114 +msgid "" +"Hide the field in question however, technically still allows setting the " +"field." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:119 +msgid "" +"The field is **not** gone and still contains any value it provides! You may " +"want to consider *remove* instead." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "remove |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "Entirely removes the field. The field value will no get evaluated." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "set mandatory |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:126 +msgid "Sets the field to mandatory." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "set optional |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:129 +msgid "Sets the field to optional." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "add option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:132 +msgid "Allows adding options to tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:136 +msgid "" +"This requires options to be hidden beforehand (remove option). It allows to " +"use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "Allows removing options from tree selects or selects." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "It allows to use *existing* configured values." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "set fixed to |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Reduces the available options by your selection." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:151 +msgid "" +"This may indirectly reduce your workflows in terms of *add option* and " +"*remove option*. 🤓" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "fill in |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:155 +msgid "Allows population of string and integer fields with your value." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:159 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:158 +msgid "" +"Allows population of string and integer fields with your value **if the " +"field is empty**." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:162 +msgid "Select a specific value within a select, tree select or boolean fields." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "auto select |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "Helps the user on tree selects and select fields:" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "" +"If the field has one option to select only and has no value yet, the value " +"is automatically set." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:171 +msgid "" +"This option only works if you have one value and acts passively with more " +"options." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:175 +msgid "Allows you to display an attribute as read only." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:179 +msgid "unset readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:178 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with above option." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:190 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:192 +msgid "" +"Stop evaluation of other, following workflows that would match otherwise." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:194 +msgid "Default: ``no``" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:199 +msgid "" +"You decide at which point your workflow is evaluated. Priorities are sorted " +"descending – this means that a workflow matching can stop matching in " +"specific situations." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:203 +msgid "Default: ``500``" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some of the ideas we had for Core Workflows. Of course " +"you can build much more complex workflows." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:13 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:21 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:67 +msgid "Group specific values and fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:27 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:32 +msgid "Workflow 2nd Level group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:34 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:42 +msgid "Workflow Support group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:44 +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:52 +msgid "Workflow Sales group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:54 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." +msgstr "" + +#: ../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:67 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:62 +msgid "" +"This is what the agent would experience with the above workflows in place." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:89 +msgid "Approval process" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:70 +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/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:80 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:83 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." +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" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:101 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:92 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." +msgstr "" + +#: ../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 "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" +msgstr "" + +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows does not replace Trigger" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 +msgid "" +"Workflows manipulate behavior of fields, however, they do not set values in " +"fields because of actions." +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" + +#: ../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:27 +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:25 +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/core-workflows/limitations.rst:35 +msgid "What is out of scope of Core Workflows...?" +msgstr "" + +#: ../system/core-workflows/limitations.rst:30 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger`, :doc:`/manage/scheduler` or over the current top." +msgstr "" + +#: ../system/core-workflows/limitations.rst:33 +msgid "Such as (but not limited to):" +msgstr "" + +#: ../system/core-workflows/limitations.rst:35 +msgid "up- or downgrade permissions of users" +msgstr "" + +#: ../system/core-workflows/limitations.rst:36 +msgid "affect article creation or listing" +msgstr "" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +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**." +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "" + +#: ../system/data-privacy.rst:12 +msgid "" +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." +msgstr "" + +#: ../system/data-privacy.rst:15 +msgid "🤔 **Huh? I don’t see the Data Privacy panel...**" +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." +msgstr "" + +#: ../system/data-privacy.rst:20 +msgid "" +"On older systems that have not been updated yet, customers can also be " +"`deleted via the Zammad console`_." +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "Deleting Users" +msgstr "" + +#: ../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 cancelled or undone." +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." +msgstr "" + +#: ../system/data-privacy.rst:36 +msgid "🙅 **The following records cannot be deleted:**" +msgstr "" + +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "" + +#: ../system/data-privacy.rst:39 +msgid "the system’s last remaining administrator account" +msgstr "" + +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a user / confirm deletion" +msgstr "" + +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "" + +#: ../system/data-privacy.rst:46 +msgid "**from the user’s profile**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "" + +#: ../system/data-privacy.rst:52 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:54 +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/data-privacy.rst:60 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "" + +#: ../system/data-privacy.rst:62 ../system/data-privacy.rst:105 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "" + +#: ../system/data-privacy.rst:68 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" + +#: ../system/data-privacy.rst:70 +msgid "👥 **You can delete organizations, too.**" +msgstr "" + +#: ../system/data-privacy.rst:72 +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/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:80 +msgid "" +"(If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization.)" +msgstr "" + +#: ../system/data-privacy.rst:85 +msgid "Step 2: Monitor deletion job status" +msgstr "" + +#: ../system/data-privacy.rst:87 +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:99 +msgid "**in the Activity Stream**" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:97 +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/data-privacy.rst:99 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." +msgstr "" + +#: ../system/data-privacy.rst:108 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../system/data-privacy.rst:122 +msgid "🤓 What happens if I receive an email from a deleted customer?" +msgstr "" + +#: ../system/data-privacy.rst:111 +msgid "" +"Zammad automatically creates a new user account whenever it receives a " +"message from an unrecognized email address, including deleted users. Deleted " +"users are never blocked from creating new tickets." +msgstr "" + +#: ../system/data-privacy.rst:116 +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/data-privacy.rst:131 +msgid "" +"🤔 What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" + +#: ../system/data-privacy.rst:127 +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/data-privacy.rst:138 +msgid "😵 I deleted an user and can still see a message they sent!" +msgstr "" + +#: ../system/data-privacy.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." +msgstr "" + +#: ../system/data-privacy.rst:142 +msgid "🚮 I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:141 +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?" +msgstr "" + +#: ../system/data-privacy.rst:145 +msgid "Please see the on-premise data section of the `data privacy`_ section." +msgstr "" + +#: ../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 "" + +#: ../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/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../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/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 "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"(You may choose from the seven built-in ticket states, but if you change " +"this setting from the default, you’ll more likely want to `define a new " +"ticket state`_ for this purpose. This can be especially useful for tracking " +"tickets with :doc:`reports `.)" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:38 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:77 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"If you’re having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot. 🙌" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:47 +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/checkmk/api-reference.rst:2 +msgid "API Reference" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +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**." +msgstr "" + +#: ../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/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/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/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/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/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +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 "" + +#: ../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/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +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:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +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_*``)." +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 "" + +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / ``" +"$NOTIFY_HOSTPROBLEMID``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. (``" +"$NOTIFY_HOSTNAME``)" +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 ”)." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. (``" +"$NOTIFY_SERVICEDESC``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "" + +#: ../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 "" + +#: ../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/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/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. (``" +"$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:113 +msgid "Ticket Attributes" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." +msgstr "" + +#: ../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 "" +"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/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/checkmk/api-reference.rst:135 +msgid "In most cases, you’ll probably want to set one of the following:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:138 +#: ../system/integrations/checkmk/api-reference.rst:172 +msgid "owner" +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 +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 "🙅 The following attributes are **not customizable**:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:150 +msgid "customer" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "How do I know what values I can set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +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!" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +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." +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +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:194 +msgid "Everything Else" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the `rails " +"console`_. Valid values are those that you can set with a string:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:220 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +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:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "Multiple alerts, same ticket." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +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." +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)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:19 +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:28 +msgid "Checkmk \"New Rule\" dialog" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:28 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:31 +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/checkmk/setup-guide.rst:35 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:42 +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/checkmk/setup-guide.rst:62 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:48 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "Host notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:65 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "🤔 **What’s with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:81 +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/checkmk/setup-guide.rst:87 +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/checkmk/setup-guide.rst:92 +msgid "Email Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:96 +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/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 "" + +#: ../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/clearbit.rst:9 +msgid "Avatar" +msgstr "" + +#: ../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/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/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/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/clearbit.rst:31 +msgid "Configuration" +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." +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." +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`." +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 "" + +#: ../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:65 +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/clearbit.rst:71 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" + +#: ../system/integrations/clearbit.rst:76 +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/clearbit.rst:81 +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:87 +msgid "Example when adding a user" +msgstr "" + +#: ../system/integrations/clearbit.rst:89 +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. Really cool, " +"right?" +msgstr "" + +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +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 dialogue or the user profile." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the `user documentation`_." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:11 +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:" +msgstr "" + +#: ../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 "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." +msgstr "" + +#: ../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/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 "" +"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." +msgstr "" + +#: ../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 "" + +#: ../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 `CTI-API documentation`_." +msgstr "" + +#: ../system/integrations/cti/generic.rst:24 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"Click the button next to the ``CTI (generic)`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/generic.rst:36 +#: ../system/integrations/cti/placetel.rst:46 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Endpoint Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:32 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." +msgstr "" + +#: ../system/integrations/cti/generic.rst:35 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see `CTI-API " +"documentation`_." +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!" +msgstr "" + +#: ../system/integrations/cti/generic.rst:58 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:57 +msgid "Call Settings" +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:42 +#: ../system/integrations/cti/sipgate.rst:55 +msgid "Inbound" +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." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Caller ID to block" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:9 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." +msgstr "" + +#: ../system/integrations/cti/generic.rst:50 +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:54 +msgid "To callers this usually will feel like the line is busy." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:19 +#: ../system/integrations/cti/sipgate.rst:45 +msgid "Outbound" +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." +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:13 +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." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``49*`` for Germany" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:12 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:13 +msgid "``33*`` for France" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:16 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:20 +msgid "Provide a short description for fellow administrators." +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 `CTI API`_ in case you're not sure." +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 +#: ../system/integrations/cti/placetel.rst:59 +#: ../system/integrations/cti/sipgate.rst:64 +msgid "Other Settings" +msgstr "" + +#: ../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/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/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 "" +"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)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:88 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:70 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." +msgstr "" + +#: ../system/integrations/cti/generic.rst:73 +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/integrations/cti/generic.rst:79 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:78 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." +msgstr "" + +#: ../system/integrations/cti/generic.rst:84 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.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." +msgstr "" + +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" +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 "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +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." +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/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 "" +"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/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 "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialogue or open the user profile for the agent that " +"picks up the call." +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 "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:10 +msgid "The agent perspective is described within our `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." +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`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:31 +msgid "" +"Click the button next to the ``Placetel`` heading to activate or deactivate " +"this function." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:37 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:42 +#: ../system/integrations/i-doit.rst:61 +msgid "Endpoint" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:41 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:46 +msgid "API Token" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:45 +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:76 +#: ../system/integrations/cti/sipgate.rst:82 +msgid "Phone Extension to Agent Mapping" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:69 +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:73 +msgid "Combine these two like so: ``@``." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface`_." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:30 +msgid "Step 1: Activate Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:15 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:18 +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/integrations/cti/provider-configurations/placetel.rst:22 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:25 +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/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:52 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:33 +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/integrations/cti/provider-configurations/placetel.rst:38 +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/integrations/cti/provider-configurations/placetel.rst:42 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:45 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:48 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:74 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:55 +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/integrations/cti/provider-configurations/placetel.rst:59 +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/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:67 +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/integrations/cti/provider-configurations/placetel.rst:70 +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:78 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +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/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/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/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "Step 1: Book sipgate.io package" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:16 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:18 +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: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." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:26 +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/integrations/cti/provider-configurations/sipgate.rst:33 +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/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:55 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:41 +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:45 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:46 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:50 +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/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:58 +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/integrations/cti/provider-configurations/sipgate.rst:62 +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/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/integrations/cti/provider-configurations/sipgate.rst:71 +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:76 +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/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:84 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:83 +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/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/integrations/cti/sipgate.rst:18 +msgid "Zammad requires a ``sipgate.io`` addon from the feature store." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:18 +msgid "" +"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." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:34 +msgid "" +"Click the button next to the ``sipgate.io`` heading to activate or " +"deactivate this function." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:38 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:42 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:45 +msgid "This endpoint is required for outgoing call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:74 +msgid "" +"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/integrations/cti/sipgate.rst:82 +msgid "Users with several devices also have several SIP-IDs." +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our `Grafana `_ setup page as well." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:11 +#: ../system/subscription/index.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +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." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 +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" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch access" +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." +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" +msgstr "" + +#: ../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 "" + +#: ../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" +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 "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "" + +#: ../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 "" + +#: ../system/integrations/elasticsearch.rst:74 +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 so: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:79 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:127 +msgid "Credentials" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:129 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." +msgstr "" + +#: ../system/integrations/elasticsearch.rst:133 +msgid "**🔐 I need my Elasticsearch user password to be changed**" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:135 +msgid "" +"Within the credentials table use the \"Reset password\" button to receive 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/integrations/elasticsearch.rst:140 +msgid "🤓 *Above does not change indexes.*" +msgstr "" + +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 +msgid "" +"With our Exchange integration, you can easily use existing address books " +"without having to update more than one source." +msgstr "" + +#: ../system/integrations/exchange.rst:9 +msgid "" +"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/integrations/exchange.rst:15 +msgid "" +"The Exchange sync is one way: Exchange => Zammad. Changes to your users " +"inside of Zammad might be overwritten by the Exchange Sync." +msgstr "" + +#: ../system/integrations/exchange.rst:19 +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 step " +"Zammad will ask you for the address book(s) and your wanted 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/integrations/exchange.rst:30 +msgid "" +"Please 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." +msgstr "" + +#: ../system/integrations/exchange.rst:35 +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/integrations/exchange.rst:42 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just normal users." +msgstr "" + +#: ../system/integrations/exchange.rst:47 +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/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "" + +#: ../system/integrations/github.rst:13 +msgid "GitHub integration does not support pull requests." +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 "" + +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "" + +#: ../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/integrations/github.rst:36 +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:42 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" + +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad’s GitHub integration" +msgstr "" + +#: ../system/integrations/github.rst:51 +msgid "" +"Leave the default API endpoint (``https://api.github.com/graphql``) as-is " +"unless you’re using GitHub Enterprise Server." +msgstr "" + +#: ../system/integrations/github.rst:54 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" + +#: ../system/integrations/github.rst:63 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "" + +#: ../system/integrations/github.rst:60 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" + +#: ../system/integrations/github.rst:62 +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:66 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:66 ../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." +msgstr "" + +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" + +#: ../system/integrations/gitlab.rst:13 +msgid "GitLab integration does not support merge requests." +msgstr "" + +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "" + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" + +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" + +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad’s GitLab integration" +msgstr "" + +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Leave the default API endpoint (``https://gitlab.com/api/graphql``) as-is " +"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/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/integrations/i-doit.rst:2 +msgid "i-doit" +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." +msgstr "" + +#: ../system/integrations/i-doit.rst:11 +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:15 +msgid "Zammad gives you two:" +msgstr "" + +#: ../system/integrations/i-doit.rst:18 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "" + +#: ../system/integrations/i-doit.rst:21 ../system/integrations/i-doit.rst:81 +msgid "What users see" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "i-doit integration in Zammad’s ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:27 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" + +#: ../system/integrations/i-doit.rst:29 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:38 ../system/integrations/i-doit.rst:92 +msgid "How to set it up" +msgstr "" + +#: ../system/integrations/i-doit.rst:40 +msgid "🧩 **Requires i-doit’s** `API Add-on`_." +msgstr "" + +#: ../system/integrations/i-doit.rst:42 +msgid "Use the following settings:" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 +msgid "Yes" +msgstr "" + +#: ../system/integrations/i-doit.rst:47 +msgid "Enforce autentication by username and password" +msgstr "" + +#: ../system/integrations/i-doit.rst:48 +msgid "No" +msgstr "" + +#: ../system/integrations/i-doit.rst:53 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "" + +#: ../system/integrations/i-doit.rst:61 +msgid "The root URL of your i-doit installation." +msgstr "" + +#: ../system/integrations/i-doit.rst:70 +msgid "API token" +msgstr "" + +#: ../system/integrations/i-doit.rst:64 +msgid "" +"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/integrations/i-doit.rst:75 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:73 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:75 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:78 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit’s device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:87 +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 " +"documentation`_ to learn how it works in practice)." +msgstr "" + +#: ../system/integrations/i-doit.rst:94 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" + +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "TTS-Type" +msgstr "" + +#: ../system/integrations/i-doit.rst:103 +msgid "``Zammad``" +msgstr "" + +#: ../system/integrations/i-doit.rst:116 +msgid "Username / Password" +msgstr "" + +#: ../system/integrations/i-doit.rst:106 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:110 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +msgstr "" + +#: ../system/integrations/i-doit.rst:114 +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:118 +msgid "URL incl. protocol" +msgstr "" + +#: ../system/integrations/i-doit.rst:119 +msgid "``https://your.zammad.domain``" +msgstr "" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." +msgstr "" + +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "" + +#: ../system/integrations/index.rst:10 +msgid "Integrations for phone systems" +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 "" + +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? `Consider creating a feature request in " +"the Zammad Community`_." +msgstr "" + +#: ../system/integrations/index.rst:33 +msgid "Integrations for authentication and customers" +msgstr "" + +#: ../system/integrations/index.rst:45 +msgid "Integrations for Monitoring Systems" +msgstr "" + +#: ../system/integrations/index.rst:47 +msgid "This section currently misses the following integrations:" +msgstr "" + +#: ../system/integrations/index.rst:49 +msgid "Icinga" +msgstr "" + +#: ../system/integrations/index.rst:50 +msgid "Monit" +msgstr "" + +#: ../system/integrations/index.rst:51 +msgid "Nagios" +msgstr "" + +#: ../system/integrations/index.rst:61 +msgid "Integrations for Issue Trackers" +msgstr "" + +#: ../system/integrations/index.rst:71 +msgid "Other Integrations" +msgstr "" + +#: ../system/integrations/index.rst:73 +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" +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." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's `Kerberos Single " +"Sign-On`_ but also works as addition to other :doc:`/settings/security/third-" +"party`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "📝 :doc:`manage`" +msgstr "" + +#: ../system/integrations/ldap/index.rst:28 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:33 +msgid "Before you continue, please note the following limitations." +msgstr "" + +#: ../system/integrations/ldap/index.rst:35 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "" + +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:42 +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:44 +msgid "Nested groups are not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:45 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" + +#: ../system/integrations/ldap/index.rst:46 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:47 +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/integrations/ldap/index.rst:53 +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:57 +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/integrations/ldap/index.rst:61 +msgid "This is subject to change with `Issue 4109`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:62 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." +msgstr "" + +#: ../system/integrations/ldap/index.rst:65 +msgid "This is subject to change with `Issue 4108`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:66 +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/integrations/ldap/index.rst:70 +msgid "This is subject to improve with `Issue 4107`_ in the future." +msgstr "" + +#: ../system/integrations/ldap/index.rst:79 +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/integrations/ldap/index.rst:83 +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/integrations/ldap/index.rst:88 +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/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:52 +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 " +"installations. 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/integrations/ldap/manage.rst:14 +msgid "" +"If you want to use LDAPs, type ``ldaps://`` instead of ``ldap://`` in front " +"of your hostname. You can also tell Zammad to use a different port by " +"appending ``:``." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:18 +msgid "" +"When providing a LDAPs source, Zammad will display an additional option *SSL " +"verification* that allows you to disable the verification for e.g. self-" +"signed SSL certificates." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:24 +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/integrations/ldap/manage.rst:36 +msgid "This especially affects inactive users" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:28 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:31 +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/integrations/ldap/manage.rst:35 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +msgid "Active Directory admins" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:39 +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:44 +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/integrations/ldap/manage.rst:48 +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" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:71 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:58 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:60 +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/integrations/ldap/manage.rst:66 +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." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:79 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:74 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:91 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:82 +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/integrations/ldap/manage.rst:88 +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/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "" + +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to `pre-defined webhooks`_ instead. Existing Slack " +"integrations should be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.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`` ." +msgstr "" + +#: ../system/integrations/slack.rst:19 +msgid "Why do I need this feature?" +msgstr "" + +#: ../system/integrations/slack.rst:21 +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:25 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:27 +msgid "on reached reminders" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:29 +msgid "a Ticket is going to escalate" +msgstr "" + +#: ../system/integrations/slack.rst:31 +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/integrations/slack.rst:35 +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/integrations/slack.rst:39 +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/integrations/slack.rst:45 +msgid "Configure the integration" +msgstr "" + +#: ../system/integrations/slack.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." +msgstr "" + +#: ../system/integrations/slack.rst:51 +msgid "" +"Choose (or create) the channel Zamma 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/integrations/slack.rst:57 +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/integrations/slack.rst:64 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." +msgstr "" + +#: ../system/integrations/slack.rst:67 +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/integrations/slack.rst:75 +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/integrations/slack.rst:82 +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/integrations/slack.rst:91 +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/integrations/slack.rst:97 +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/integrations/slack.rst:103 +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" +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." +msgstr "" + +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../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/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message’s **integrity** and **authenticity**." +msgstr "" + +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "" + +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." +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" +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." +msgstr "" + +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr "" + +#: ../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/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." +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr "" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "" + +#: ../system/integrations/smime/index.rst:41 +msgid "Usage" +msgstr "" + +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works in practice, see the `user " +"docs `_." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:4 +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" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate data" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +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." +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." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../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/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +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/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +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." +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/smime/manage-certificates.rst:65 +msgid "**🔐 Passphrase-protected private keys stay protected**" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:67 +msgid "" +"Downloading private keys that originally were encrypted with a passphrase " +"will also have this state after retrieval. Knowing the password is mandatory " +"to continue working with keys in question." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:75 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "Default Behavior" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:80 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:84 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behaviour on per group basis" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:91 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:2 +msgid "Prerequisites" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I’m new to S/MIME. Where can I get a certificate?**" +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:" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +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**." +msgstr "" + +#: ../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/integrations/smime/prerequisites.rst:34 +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:38 +msgid "This is by design and can't be adjusted." +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 "" + +#: ../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 "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +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``." +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/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" +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 "" + +#: ../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/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" + +#: ../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/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven’t added this certificate already?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" + +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "" + +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "" + +#: ../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 "" +"2. 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/integrations/zabbix.rst:27 +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/integrations/zabbix.rst:33 +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:" +msgstr "" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" + +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" + +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +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." +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 "" + +#: ../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." +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." +msgstr "" + +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" + +#: ../system/integrations/zabbix.rst:61 +msgid "For more information, use the `Zabbix documentation`_." +msgstr "" + +#: ../system/maintenance.rst:2 +msgid "Maintenance" +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." +msgstr "" + +#: ../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/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 +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" +msgstr "" + +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "" + +#: ../system/monitoring.rst:4 +msgid "" +"**Please note:** This is only available in self hosted instances, as we're " +"monitoring hosted instances and fix problems." +msgstr "" + +#: ../system/monitoring.rst:6 +msgid "" +"On the monitoring page you can see the current health state of Zammad. This " +"can be useful if you for example have the feeling that you don't receive " +"emails anymore, you can take a look here before logging onto your Server." +msgstr "" + +#: ../system/monitoring.rst:9 +msgid "" +"Besides the optical state of an event, you can also reset the access token " +"for this module and get the monitoring URL for a monitoring system of your " +"choice." +msgstr "" + +#: ../system/monitoring.rst:11 +msgid "Example output to this can be:" +msgstr "" + +#: ../system/monitoring.rst:13 +msgid "Everything is OK (refer to image 2 for interface example)::" +msgstr "" + +#: ../system/monitoring.rst:17 +msgid "" +"Zammad has issue (whatever nature, refer to image 2 for interface example)::" +msgstr "" + +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups. This can be useful if you need to add further information to a " +"ticket that you don't want to have in a note (you'll find it easier)." +msgstr "" + +#: ../system/objects.rst:10 +msgid "" +"Try to avoid deleting objects (and disable them instead) as Zammad might run " +"into unexpected conditions if they are referenced somewhere." +msgstr "" + +#: ../system/objects.rst:15 +msgid "" +"Here's an overview of the objects. On the upper right you can add new " +"Attributes. By default, there will be no custom fields - standard objects " +"will be grayed out, you can't delete or change those. Custom objects (will " +"be displayed in black font and have a trash bin on the right site to delete " +"unnecessary objects. By clicking on \"custom objects\" you can edit them to " +"suit your needs." +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." +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 "" + +#: ../system/objects.rst:40 +msgid "Ordering objects" +msgstr "" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for objects has become more important than ever." +msgstr "" + +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of an object, simply click on the object entry in " +"question, scroll down and adjust the position number." +msgstr "" + +#: ../system/objects.rst:None +msgid "" +"Screenshot showing object entries with a custom object ordered in between " +"default objects" +msgstr "" + +#: ../system/objects.rst:53 +msgid "" +"In case two objects have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" + +#: ../system/objects.rst:0 +msgid "**Limitation**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"Please note that you cannot change the positioning of default objects at " +"this time." +msgstr "" + +#: ../system/objects.rst:61 +msgid "Updating database after adding or editing objects" +msgstr "" + +#: ../system/objects.rst:63 +msgid "" +"When adding or changing objects, Zammad will not apply the changes " +"instantly, but instead shows you the changed objects 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/objects.rst:71 +msgid "" +"After applying the object 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 those kind of " +"configurations during maintenance windows." +msgstr "" + +#: ../system/objects.rst:79 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" + +#: ../system/objects.rst:82 +msgid "**🤓 Service restarts can be automated**" +msgstr "" + +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" + +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use `environment " +"variables`_" +msgstr "" + +#: ../system/objects.rst:92 +msgid "System objects" +msgstr "" + +#: ../system/objects.rst:94 +msgid "" +"Zammad comes with pre-configured objects. Some of these currently do not " +"provide the possibility to edit them via UI (or at all)." +msgstr "" + +#: ../system/objects.rst:97 +msgid "This is not a bug but is to save you from possibly nuking Zammad." +msgstr "" + +#: ../system/objects.rst:101 +msgid "" +"There are technical exceptions which can be solved via console. This e.g. " +"affects ticket states and priorities, see `console section`_." +msgstr "" + +#: ../system/objects.rst:104 +msgid "💰 If you're a hosted customer, please contact your support for more. 💰" +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." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This object allows position of its values ↔️**" +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and to the values." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:5 +msgid "" +"Use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. By this you can cycle through the " +"available layers." +msgstr "" + +#: ../system/objects/includes/reposition-treeselect-values.include.rst:9 +msgid "When you're ready, submit your changes to save the object." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the fields options, edit the field and scroll below " +"the values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" + +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual position you did above will be " +"lost upon saving! ☠️" +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." +msgstr "" + +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" + +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" + +#: ../system/objects/permissions.rst:2 +msgid "Object permissions" +msgstr "" + +#: ../system/objects/permissions.rst:7 +msgid "Some of the possible permission and screen options for objects." +msgstr "" + +#: ../system/objects/permissions.rst:9 +msgid "" +"Whenever needed you can restrict access to objects based on the :ref:`user " +"permission ` (``admin``, ``ticket.agent`` & ``ticket." +"customer``)." +msgstr "" + +#: ../system/objects/permissions.rst:13 +msgid "**🤓 Below is not set in stone 🤓**" +msgstr "" + +#: ../system/objects/permissions.rst:15 +msgid "" +"You can always adjust below settings with :doc:`/system/core-workflows`. " +"This also allows role based restriction. 👀" +msgstr "" + +#: ../system/objects/permissions.rst:20 +msgid "" +"In some situations, Zammad internally overrules below screen, requirement " +"and permission settings. This is because at some points you can't set fields " +"which would mean we couldn't create the ticket." +msgstr "" + +#: ../system/objects/permissions.rst:24 +msgid "This currently affects:" +msgstr "" + +#: ../system/objects/permissions.rst:26 +msgid "merging" +msgstr "" + +#: ../system/objects/permissions.rst:27 +msgid "emails no matter of the originating channel (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:28 +msgid ":doc:`/channels/form` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:29 +msgid ":doc:`/channels/facebook` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:30 +msgid ":doc:`/channels/telegram` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:31 +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:32 +msgid "SMS (incoming)" +msgstr "" + +#: ../system/objects/permissions.rst:35 +msgid "About screens" +msgstr "" + +#: ../system/objects/permissions.rst:37 +msgid "Zammad cares about the screen you're going to use the object in." +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" + +#: ../system/objects/permissions.rst:40 +msgid "Every time you use a creation dialogue for not yet existing data." +msgstr "" + +#: ../system/objects/permissions.rst:44 +msgid "edit" +msgstr "" + +#: ../system/objects/permissions.rst:43 +msgid "" +"Every time you're editing existing data - viewing existing tickets counts as " +"edit screen." +msgstr "" + +#: ../system/objects/permissions.rst:55 +msgid "view" +msgstr "" + +#: ../system/objects/permissions.rst:47 +msgid "Affects view screens of existing data like e.g. user profiles." +msgstr "" + +#: ../system/objects/permissions.rst:51 +msgid "This setting is available for the following object contexts:" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "invite_customer & invite_agent" +msgstr "" + +#: ../system/objects/permissions.rst:58 +msgid "" +"Shown when using the invitation dialogue from \"First Steps\" in the " +"dashboard." +msgstr "" + +#: ../system/objects/permissions.rst:61 +msgid "About screen options" +msgstr "" + +#: ../system/objects/permissions.rst:63 +msgid "" +"Now that we know the different possible situations, let's talk about " +"available options." +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "shown" +msgstr "" + +#: ../system/objects/permissions.rst:67 +msgid "Show or hide a field." +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "required" +msgstr "" + +#: ../system/objects/permissions.rst:70 +msgid "" +"Set a field to mandatory. Forces users (via UI and API) to populate the " +"field." +msgstr "" + +#: ../system/objects/types.rst:2 +msgid "Object types" +msgstr "" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object, you can choose between the following object types." +msgstr "" + +#: ../system/objects/types.rst:8 +msgid "" +"You cannot change the object format / type as soon as it is applied. If you " +"no longer need an object, consider disabling it instead of removing." +msgstr "" + +#: ../system/objects/types.rst:12 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Allows setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" + +#: ../system/objects/types.rst:19 +msgid "Provides a date picker field and does not allow default values." +msgstr "" + +#: ../system/objects/types.rst:23 +msgid "Default time diff (hours)" +msgstr "" + +#: ../system/objects/types.rst:22 +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" +msgstr "" + +#: ../system/objects/types.rst:44 +msgid "Date & time field" +msgstr "" + +#: ../system/objects/types.rst:29 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" + +#: ../system/objects/types.rst:33 +msgid "Allow future" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" + +#: ../system/objects/types.rst:37 +msgid "Allow past" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" + +#: ../system/objects/types.rst:41 +msgid "Default time diff (minutes)" +msgstr "" + +#: ../system/objects/types.rst:40 +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 & time fields" +msgstr "" + +#: ../system/objects/types.rst:47 +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:51 +msgid "Minimal" +msgstr "" + +#: ../system/objects/types.rst:51 +msgid "The minimal value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "Maximal" +msgstr "" + +#: ../system/objects/types.rst:54 +msgid "The maximum value the field accepts." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" + +#: ../system/objects/types.rst:60 +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/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "" + +#: ../system/objects/types.rst:73 +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" +msgstr "" + +#: ../system/objects/types.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." +msgstr "" + +#: ../system/objects/types.rst:91 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" + +#: ../system/objects/types.rst:94 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" + +#: ../system/objects/types.rst:96 +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:101 +msgid "Default" +msgstr "" + +#: ../system/objects/types.rst:100 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:105 ../system/objects/types.rst:131 +msgid "Maxlength" +msgstr "" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:131 +msgid "You can pick the maximum length of the field." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" + +#: ../system/objects/types.rst:110 +msgid "Rows" +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/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "" + +#: ../system/objects/types.rst:136 +msgid "Text field" +msgstr "" + +#: ../system/objects/types.rst:116 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" + +#: ../system/objects/types.rst:119 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" + +#: ../system/objects/types.rst:123 +msgid "Currently available:" +msgstr "" + +#: ../system/objects/types.rst:126 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:127 +msgid "Text" +msgstr "" + +#: ../system/objects/types.rst:128 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" + +#: ../system/objects/types.rst:139 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" + +#: ../system/objects/types.rst:148 +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/objects/types.rst:159 +msgid "URL fields (Link-Template)" +msgstr "" + +#: ../system/objects/types.rst:163 +msgid "This function is restricted to Text and Select objects only." +msgstr "" + +#: ../system/objects/types.rst:165 +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/objects/types.rst:171 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" + +#: ../system/objects/types.rst:174 +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/objects/types.rst:179 +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/objects/types.rst:184 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" + +#: ../system/objects/types.rst:186 +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/objects/types.rst:191 +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/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" + +#: ../system/objects/types.rst:203 +msgid "How does this work...?!" +msgstr "" + +#: ../system/objects/types.rst:205 +msgid "" +"As an example, let's say you have an object called ``amazingobject`` - you " +"want to open a google search directly with the input from that field." +msgstr "" + +#: ../system/objects/types.rst:208 +msgid "" +"Providing below to the link-template field allows you to do so: ``https://" +"www.google.com/search?q=#{ticket.amazingobject}``" +msgstr "" + +#: ../system/objects/types.rst:213 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" + +#: ../system/objects/types.rst:216 +msgid "The result will look as follows." +msgstr "" + +#: ../system/objects/types.rst:221 +msgid "" +"The above screencast shows how the link template will perform after object " +"creation." +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 "" + +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" + +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these." +msgstr "" + +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" + +#: ../system/sessions.rst:14 +msgid "" +"This page indirectly is affected by :ref:`security_session_timeout` " +"configurations from security settings." +msgstr "" + +#: ../system/sessions.rst:17 +msgid "Zammad will provide the following information:" +msgstr "" + +#: ../system/sessions.rst:20 +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/sessions.rst:26 +msgid "Browser" +msgstr "" + +#: ../system/sessions.rst:26 +msgid "The browser agent communicated to Zammad." +msgstr "" + +#: ../system/sessions.rst:47 +msgid "Location" +msgstr "" + +#: ../system/sessions.rst:29 +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:33 +msgid "The following information can be shown:" +msgstr "" + +#: ../system/sessions.rst:37 +msgid "IP address" +msgstr "" + +#: ../system/sessions.rst:36 +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/sessions.rst:47 +msgid "Country (or Country + City)" +msgstr "" + +#: ../system/sessions.rst:40 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" + +#: ../system/sessions.rst:45 +msgid "" +"Depending on how long the address is assigned to a specific country the " +"result may differ. Results can be inaccurate - this technically is not an " +"error." +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Age" +msgstr "" + +#: ../system/sessions.rst:50 +msgid "Provides the time when the session initially has been created." +msgstr "" + +#: ../system/sessions.rst:59 +msgid "Update" +msgstr "" + +#: ../system/sessions.rst:53 +msgid "" +"Provides the time the user last 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/sessions.rst:59 +msgid "This timestamp is being used for the session timeout." +msgstr "" + +#: ../system/sessions.rst:62 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" + +#: ../system/subscription/billing.rst:2 +msgid "Billing" +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." +msgstr "" + +#: ../system/subscription/billing.rst:37 +msgid "Billing information" +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`_." +msgstr "" + +#: ../system/subscription/billing.rst:16 +msgid "Billing address" +msgstr "" + +#: ../system/subscription/billing.rst:15 +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/subscription/billing.rst:20 +msgid "VAT ID" +msgstr "" + +#: ../system/subscription/billing.rst:19 +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/subscription/billing.rst:31 +msgid "Billing Email Address" +msgstr "" + +#: ../system/subscription/billing.rst:23 +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/subscription/billing.rst:27 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:31 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" + +#: ../system/subscription/billing.rst:33 +msgid "" +"Don't forget to press the *Submit* button after you changed above settings." +msgstr "" + +#: ../system/subscription/billing.rst:0 +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" + +#: ../system/subscription/billing.rst:74 +msgid "Payment history" +msgstr "" + +#: ../system/subscription/billing.rst:40 +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/subscription/billing.rst:45 +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:50 +msgid "Date" +msgstr "" + +#: ../system/subscription/billing.rst:50 +msgid "Date of the invoice creation." +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Amount" +msgstr "" + +#: ../system/subscription/billing.rst:53 +msgid "Invoice total including VAT if applicable." +msgstr "" + +#: ../system/subscription/billing.rst:56 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" + +#: ../system/subscription/billing.rst:67 +msgid "Payment method / Service period" +msgstr "" + +#: ../system/subscription/billing.rst:60 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" + +#: ../system/subscription/billing.rst:65 +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:71 +msgid "Receipt" +msgstr "" + +#: ../system/subscription/billing.rst:70 +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:98 +msgid "Do you want to cancel your subscription?" +msgstr "" + +#: ../system/subscription/billing.rst:77 +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." +msgstr "" + +#: ../system/subscription/billing.rst:80 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" + +#: ../system/subscription/billing.rst:84 +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:91 +msgid "**😖 Cancelled by accident?**" +msgstr "" + +#: ../system/subscription/billing.rst:93 +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/subscription/billing.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" + +#: ../system/subscription/index.rst:2 +msgid "Subscription (SaaS)" +msgstr "" + +#: ../system/subscription/index.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +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`_." +msgstr "" + +#: ../system/subscription/index.rst:23 +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:28 +msgid ":doc:`💰 Subscription plan `" +msgstr "" + +#: ../system/subscription/index.rst:27 +msgid "" +"Everything affecting your instance subscription functions like number of " +"agents, package and payment method." +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid ":doc:`🧾 Subscription billing `" +msgstr "" + +#: ../system/subscription/index.rst:31 +msgid "" +"Everything regarding billing address, invoices and account cancellation." +msgstr "" + +#: ../system/subscription/index.rst:36 +msgid "FAQ" +msgstr "" + +#: ../system/subscription/index.rst:40 +msgid "I set up a trial account but am missing functions to test" +msgstr "" + +#: ../system/subscription/index.rst:39 +msgid "" +"Sorry. The trial instance is running within the professional package " +"allowing up to three agents." +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "Can I change package within the trial?" +msgstr "" + +#: ../system/subscription/index.rst:43 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" + +#: ../system/subscription/index.rst:48 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" + +#: ../system/subscription/index.rst:46 +msgid "" +"Your instance will automatically be cancelled for you. Please see *What " +"happens to my instance after it has been cancelled?* for more." +msgstr "" + +#: ../system/subscription/index.rst:61 +msgid "What happens to my instance after it has been cancelled?" +msgstr "" + +#: ../system/subscription/index.rst:51 +msgid "That depends slightly on your instance state:" +msgstr "" + +#: ../system/subscription/index.rst:57 +msgid "Trial instance" +msgstr "" + +#: ../system/subscription/index.rst:54 +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:61 +msgid "Paid instance" +msgstr "" + +#: ../system/subscription/index.rst:60 +msgid "" +"If you're a paying customer and cancelled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" + +#: ../system/subscription/index.rst:63 +msgid "Can removed instances be restored?" +msgstr "" + +#: ../system/subscription/index.rst:64 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" + +#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:39 +msgid "Plan" +msgstr "" + +#: ../system/subscription/plan.rst:18 +msgid "Subscription" +msgstr "" + +#: ../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." +msgstr "" + +#: ../system/subscription/plan.rst:11 +msgid "" +"You can learn more on how to manage your agents within :doc:`user management " +"`." +msgstr "" + +#: ../system/subscription/plan.rst:14 +msgid "This list *does not* count accounts with admin permissions only." +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." +msgstr "" + +#: ../system/subscription/plan.rst:21 +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/subscription/plan.rst:25 +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/subscription/plan.rst:28 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" + +#: ../system/subscription/plan.rst:32 +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/subscription/plan.rst:0 +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" + +#: ../system/subscription/plan.rst:89 +msgid "Summary" +msgstr "" + +#: ../system/subscription/plan.rst:45 +msgid "" +"In this section you can adjust the settings of the previous selected plan." +msgstr "" + +#: ../system/subscription/plan.rst:64 +msgid "Billing cycle" +msgstr "" + +#: ../system/subscription/plan.rst:48 +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/subscription/plan.rst:53 +msgid "" +"If you're still trying out things and e.g. 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:59 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" + +#: ../system/subscription/plan.rst:63 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" + +#: ../system/subscription/plan.rst:72 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" + +#: ../system/subscription/plan.rst:67 +msgid "Choose the number of agents you require for your instance." +msgstr "" + +#: ../system/subscription/plan.rst:69 +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:75 +msgid "Total" +msgstr "" + +#: ../system/subscription/plan.rst:75 +msgid "This will be the net total you're going to be billed." +msgstr "" + +#: ../system/subscription/plan.rst:77 +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/subscription/plan.rst:83 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" + +#: ../system/subscription/plan.rst:86 +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:105 +msgid "Payment method" +msgstr "" + +#: ../system/subscription/plan.rst:92 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" + +#: ../system/subscription/plan.rst:97 +msgid "Credit card" +msgstr "" + +#: ../system/subscription/plan.rst:95 +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." +msgstr "" + +#: ../system/subscription/plan.rst:101 +msgid "SEPA" +msgstr "" + +#: ../system/subscription/plan.rst:100 +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/subscription/plan.rst:103 +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/translations.rst:2 +msgid "Translations" +msgstr "" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally on our `Weblate instance`_. " +"This allows non development people to review and update translation strings " +"of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:8 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us sorting this out! All you need is either a GitHub " +"account or register directly on our instance." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Did you know?" +msgstr "" + +#: ../system/translations.rst:0 +msgid "This is also where documentation translations are handled. 🤓" +msgstr "" + +#: ../system/translations.rst:22 +msgid "" +"Apart from these centralized translations, there's still local translations " +"you can manage. This is relevant if you added custom objects that require " +"translations or even states." +msgstr "" + +#: ../system/translations.rst:28 +msgid "" +"You can no longer synchronize these translations upstream like prior Zammad " +"5.1." +msgstr "" + +#: ../system/translations.rst:0 +msgid "Translation management page within the admin menu" +msgstr "" + +#: ../system/translations.rst:35 +msgid "How do I get the most recent translations?" +msgstr "" + +#: ../system/translations.rst:37 +msgid "" +"Because of how Zammad ships translations, the only way to update the central " +"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:43 +msgid "But... I have custom objects?!" +msgstr "" + +#: ../system/translations.rst:45 +msgid "" +"No problem at all! If you can't find the strings of your objects already " +"within the translation list, please ensure to `add the translation strings`_ " +"to your installation." +msgstr "" + +#: ../system/translations.rst:49 +msgid "Now you can translate your objects as needed." +msgstr "" + +#: ../system/translations.rst:55 +msgid "So how does this local translation work?" +msgstr "" + +#: ../system/translations.rst:57 +msgid "" +"Within the translation menu, look up the string you're searching for and " +"update its target as designed. As soon as you leave the target input field, " +"the change will be saved." +msgstr "" + +#: ../system/translations.rst:61 +msgid "" +"Such locally translated strings are slightly highlighted and come with a " +"\"Reset\" action." +msgstr "" + +#: ../system/translations.rst:64 +msgid "" +"The translation strings shown by Zammad are always those of the profile " +"language you've chosen. If you need to translate a different language, " +"change the language in your `profile settings`_ up front." +msgstr "" + +#: ../system/translations.rst:73 +msgid "" +"Due to caching you may have to reload your browser session to see the " +"changes." +msgstr "" + +#: ../system/translations.rst:76 +msgid "**Yes, these changes are update safe!**" +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing an adjusted translation locally" +msgstr "" + +#: ../system/translations.rst:82 +msgid "Reverting to original translations" +msgstr "" + +#: ../system/translations.rst:84 +msgid "" +"If you want to reset all translation changes on your instance, use the red " +"\"Reset\" button on the upper right of the translation management." +msgstr "" + +#: ../system/translations.rst:87 +msgid "" +"In case you just intend to reset a specific translation, lookup the " +"translation string and use the \"reset\" action." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing reset button highlighted" +msgstr "" + +#: ../system/variables.rst:2 +msgid "Variables" +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 `_." +msgstr "" + +#: ../system/variables.rst:7 +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 show display all variables being available within this context " +"and replace it to the variable as soon as you selected an entry." +msgstr "" + +#: ../system/variables.rst:10 +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 (in text fields `` `` is a value!)." +msgstr "" + +#: ../system/variables.rst:15 +msgid "Variable Categories" +msgstr "" + +#: ../system/variables.rst:26 +msgid "Wait, what about custom objects?" +msgstr "" + +#: ../system/variables.rst:28 +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 "" + +#: ../system/variables.rst:30 +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:33 +msgid "Ticket (``ticket``)" +msgstr "" + +#: ../system/variables.rst:34 +msgid "User (``user``)" +msgstr "" + +#: ../system/variables.rst:35 +msgid "Organization (``organization``)" +msgstr "" + +#: ../system/variables.rst:36 +msgid "Group (``group``)" +msgstr "" + +#: ../system/variables.rst:38 +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}``." +msgstr "" + +#: ../system/variables.rst:41 +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/article.rst:2 +msgid "Articles" +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 `_." +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." +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." +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/variables/article.rst:1 ../system/variables/config.rst:1 +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "variable" +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/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 +#: ../system/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +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 "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Updated" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``email`` (`list of article types `_)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > To" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > From" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Created" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Cc" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article > Text" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "" + +#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "" + +#: ../system/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "" + +#: ../system/variables/config.rst:2 +msgid "Config" +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." +msgstr "" + +#: ../system/variables/config.rst:11 +msgid "Config Variables" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Organization" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../system/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" + +#: ../system/variables/current-user.rst:2 +msgid "Current User" +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." +msgstr "" + +#: ../system/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usuage." +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." +msgstr "" + +#: ../system/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +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 "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "" + +#: ../system/variables/current-user.rst:1 +msgid "``#{user.address}``" +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." +msgstr "" + +#: ../system/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "" +"Currently not available, see `Issue 2769 `_" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > #" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +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 behaviour Settings `_ for this)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "" + +#: ../system/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" + +#: ../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 ad2d41ad..460c822b 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: 2023-05-04 16:53+0200\n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -3960,6 +3960,210 @@ msgid "" "Contact your administrator if you don’t have access to an admin account." msgstr "" +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -3985,29 +4189,37 @@ msgstr "" msgid "Microsoft 365" msgstr "" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4152,267 +4364,376 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" msgstr "" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + #: ../channels/web.rst:2 msgid "Web" msgstr "" @@ -5692,15 +6013,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -5788,7 +6109,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -5883,11 +6204,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -5901,11 +6222,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -6814,7 +7135,7 @@ msgid "``admin.channel_twitter``" msgstr "" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr "" #: ../manage/roles/admin-permissions.rst:84 @@ -9365,14 +9686,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "" @@ -9388,67 +9701,89 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9458,13 +9793,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9472,25 +9807,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9498,52 +9833,52 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9555,39 +9890,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9595,29 +9930,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9628,18 +9963,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13727,6 +14062,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "" + #: ../settings/security/third-party/twitter.rst:4 msgid "" "It is possible to create a quick login for your helpdesk via Twitter to do " @@ -18872,7 +19211,7 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" msgstr "" #: ../system/objects/permissions.rst:32 diff --git a/locale/tr/LC_MESSAGES/admin-docs.po b/locale/tr/LC_MESSAGES/admin-docs.po index 9bab51c5..3db7b938 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: 2023-05-04 16:53+0200\n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" "PO-Revision-Date: 2021-12-03 14:33+0000\n" "Last-Translator: TRANSFER FROM TRANSIFEX \n" "Language-Team: Turkish ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +#, fuzzy +#| msgid "Usage" +msgid "Error message" +msgstr "Kullanım" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +#, fuzzy +#| msgid "Request headers" +msgid "Request admin consent" +msgstr "İstek başlıkları" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +#, fuzzy +#| msgid "Port" +msgid "or" +msgstr "Port" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +#, fuzzy +#| msgid "Personal accounts" +msgid "Private email account" +msgstr "Kişisel hesaplar" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 #, fuzzy #| msgid "" @@ -4210,29 +4422,39 @@ msgstr "" msgid "Microsoft 365" msgstr "Microsoft 365" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +#, fuzzy +#| msgid ":doc:`Channels > Email `" +msgid ":doc:`🛟 Common M365 errors `" +msgstr ":doc:`Kanallar > E-posta `" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4383,11 +4605,31 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +#, fuzzy +#| msgid "Twitter" +msgid "Twitter/X" msgstr "Twitter" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" @@ -4395,11 +4637,11 @@ msgstr "" "Zammad, Twitter entegrasyonunu destekler, yani tıpkı e-postalar gibi tweet " "ve DM gönderip alabilirsiniz!" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." @@ -4408,60 +4650,60 @@ msgstr "" "tweet atmak için (bir e-posta için yaptığınız gibi) yanıtla düğmesini " "tıklamanız yeterlidir." -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "Kurulum için, aşağıdaki adımları takip et:" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "`Twitter Geliştirici hesabı`_ için uygula." -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "Zammad için `Yeni bir Twitter uygulaması oluştur`_." -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" "Yeni uygulamanızın izinlerini *Okuma, yazma ve direkt mesajlara erişim* " "olarak ayarlayın." -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "Yeni bir erişim jetonu ve sırrı oluşturun." -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "Zammad'a yeni Twitter uygulamanı ekle." -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "Zammad'a Twitter hesabınızı ekleyin." -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "1. Twitter Geliştirici hesabı için uygula" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." @@ -4469,186 +4711,186 @@ msgstr "" "Bir Geliştirici hesabı için uygulama tamamlandıktan sonra bu hoş geldiniz " "sayfası görüntülenir." -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "2. Zammad için yeni bir Twitter uygulaması oluştur" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "Uygulama adı" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "Uygulama açıklaması" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "Burada her şey yolunda." -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "Web site URL'si" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" "``https:///api/v1/external_credentials/twitter/callback``" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "3. Yeni uygulamanın izinlerini ayarla" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "*Okuma, yazma ve direkt mesajlara erişme*yi seç" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "5. Bir geliştirme ortamı oluştur" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "6. Zammad'a yeni Twitter uygulamanı ekle" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "7. Zammad'a Twitter hesabınızı ekleyin" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "8. Filtreleri yapılandır" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." @@ -4656,6 +4898,105 @@ msgstr "" "Bu kadar! Artık gelen tweet'ler ve DM'ler otomatik olarak Zammad biletlerine " "dönüştürülecek." +#: ../channels/twitter-x/twitter-x-note.rst:4 +#, fuzzy +#| msgid "Twitter" +msgid "Twitter/X note" +msgstr "Twitter" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +#, fuzzy +#| msgid "Current User > Organization > Note" +msgid "Current situation" +msgstr "Geçerli Kullanıcı > Organizasyon > Not" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +#, fuzzy +#| msgid "Features" +msgid "Future" +msgstr "Özellikler" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +#, fuzzy +#| msgid ":doc:`Channels > Twitter `" +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr ":doc:`Kanallar > Twitter `" + #: ../channels/web.rst:2 msgid "Web" msgstr "Web" @@ -5988,15 +6329,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -6090,7 +6431,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -6189,11 +6530,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "📑 Not" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -6207,11 +6548,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "▶️ Aktif" @@ -7188,7 +7529,9 @@ msgid "``admin.channel_twitter``" msgstr "``admin.channel_twitter``" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +#, fuzzy +#| msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr ":doc:`Kanallar > Twitter `" #: ../manage/roles/admin-permissions.rst:84 @@ -9956,14 +10299,6 @@ msgstr "" "Artık Almanca bildirim e-postaları gönderirken orijinal dosya yerine bu " "dosya kullanılacak." -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "Kullanıcılar" @@ -9979,67 +10314,95 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +#, fuzzy +#| msgid ":doc:`System > Integrations `" +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr ":doc:`Sistem > Entegrasyonlar `" + +#: ../manage/users/index.rst:19 +#, fuzzy +#| msgid ":doc:`System > Integrations `" +msgid ":doc:`via Exchange integration `" +msgstr ":doc:`Sistem > Entegrasyonlar `" + +#: ../manage/users/index.rst:20 +#, fuzzy +#| msgid "`System > API `_" +msgid "`via REST API `_" +msgstr "`Sistem > API `_" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "👤 Giriş" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -10049,13 +10412,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -10063,25 +10426,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "🔑 Parola" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "🏢 Organizasyon" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10089,54 +10452,54 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 #, fuzzy #| msgid "🏢 Organization" msgid "🏤 Secondary Organizations" msgstr "🏢 Organizasyon" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "👑 VIP" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10148,39 +10511,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -10188,29 +10551,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "🔓 İzinler" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -10221,18 +10584,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -14501,6 +14864,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "Twitter" + #: ../settings/security/third-party/twitter.rst:4 #, fuzzy #| msgid "" @@ -19762,8 +20129,10 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" -msgstr "" +#, fuzzy +#| msgid ":doc:`Channels > Twitter `" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" +msgstr ":doc:`Kanallar > Twitter `" #: ../system/objects/permissions.rst:32 msgid "SMS (incoming)" diff --git a/locale/zh_Hans/LC_MESSAGES/admin-docs.po b/locale/zh_Hans/LC_MESSAGES/admin-docs.po index dd7073b2..910a5612 100644 --- a/locale/zh_Hans/LC_MESSAGES/admin-docs.po +++ b/locale/zh_Hans/LC_MESSAGES/admin-docs.po @@ -7,17 +7,17 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-05-04 16:53+0200\n" -"PO-Revision-Date: 2022-11-06 16:14+0000\n" -"Last-Translator: Never Min <59808@qq.com>\n" +"POT-Creation-Date: 2023-08-25 14:57+0200\n" +"PO-Revision-Date: 2023-08-14 12:18+0000\n" +"Last-Translator: chen \n" "Language-Team: Chinese (Simplified) \n" +"projects/documentations/admin-documentation-latest/zh_Hans/>\n" "Language: zh_Hans\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" -"X-Generator: Weblate 4.14.1\n" +"X-Generator: Weblate 4.18.2\n" #: ../channels/chat.rst:2 msgid "Chat" @@ -34,78 +34,82 @@ msgstr "" #: ../channels/chat.rst:9 msgid "How to improve Support by Chat?" -msgstr "" +msgstr "如何提升在线聊天的客服水平？" #: ../channels/chat.rst:11 msgid "" "We've asked others about their opinion in our circles, to learn what people " "expect or dislike. This is what we found out:" msgstr "" +"我们已经询问了我们圈子里的其他人对此的看法，以了解人们的期望或不喜欢的地方。" +"这是我们发现的：" #: ../channels/chat.rst:18 msgid "Good experiences" -msgstr "" +msgstr "好的体验" #: ../channels/chat.rst:16 msgid "Getting personal support by a human being" -msgstr "" +msgstr "得到人工的个人支持" #: ../channels/chat.rst:17 msgid "Getting a fast response" -msgstr "" +msgstr "得到快速的回应" #: ../channels/chat.rst:18 msgid "Solving my problem quickly" -msgstr "" +msgstr "快速解决我的问题。" #: ../channels/chat.rst:26 msgid "Bad experiences" -msgstr "" +msgstr "糟糕的经历" #: ../channels/chat.rst:21 msgid "" "A chat window on a website (while the chat being offline) with the hint to " "\"Leave a message\"" -msgstr "" +msgstr "网站上的聊天窗口（聊天处于离线状态），并提示“留言”" #: ../channels/chat.rst:23 msgid "Long waiting queues before even writing with a personal" -msgstr "" +msgstr "在与个人交谈之前，需要长时间等待队列。" #: ../channels/chat.rst:24 msgid "" "Receiving a message like \"My name is Nina, what can I do for you?\" after " "sending a message with my issue." msgstr "" +"在发送了我问题的信息后，收到一条像“我叫Nina，我能为你做什么？”这样的信息。" #: ../channels/chat.rst:26 msgid "A Chat that doesn't integrate itself into the Website properly" -msgstr "" +msgstr "一个不能正确集成到网站中的聊天窗口。" #: ../channels/chat.rst:29 msgid "Our answer: The Zammad Chat Widget" -msgstr "" +msgstr "我们的答案：Zammad聊天小部件。" #: ../channels/chat.rst:31 msgid "" "The task is clear: Work on the disadvantages of a regular support chat and " "improve them." -msgstr "" +msgstr "任务很明确：针对常规支持聊天的缺点进行改进。" #: ../channels/chat.rst:48 msgid "Our approach is as follows" -msgstr "" +msgstr "我们的方法如下：" #: ../channels/chat.rst:35 msgid "" "We'll only display the chat widget, if at least one agent is available and " "the agent still has capacity." msgstr "" +"只有当至少有一名代理人可用且代理人仍有处理能力时，我们才会显示聊天小部件。" #: ../channels/chat.rst:38 msgid "" "If no agent is online or the agents are absend, the chat won't be available" -msgstr "" +msgstr "如果没有代理在线或代理人缺席，聊天将不可用。" #: ../channels/chat.rst:40 msgid "" @@ -113,6 +117,9 @@ msgid "" "requests or the WebApp is offline. This way, your support staff can take " "breaks without your customers waiting ages for a reaction (see point above)" msgstr "" +"如果代理人不接受新的聊天请求或WebApp离线，我们将设置代理人为不活跃状态。这" +"样，您的支持人员可以休息，而无需让您的客户等待很长时间才能得到反馈（见上" +"文）。" #: ../channels/chat.rst:43 msgid "" @@ -120,6 +127,8 @@ msgid "" "no strange delay coming afterwards. Zammad will fire a (configurable by " "agent) auto response as soon as the agents accepts the Chat request." msgstr "" +"为了确保后续没有奇怪的延迟，Zammad不会自动响应聊天消息。只有当代理人接受聊天" +"请求后，Zammad才会触发（由代理人配置的）自动回复。" #: ../channels/chat.rst:46 msgid "" @@ -127,22 +136,24 @@ msgid "" "adjust those colors allowing you to integrate the chat into your website, " "like it has been there before." msgstr "" +"Zammad将尝试将您的主要网站颜色适应到聊天中。您也可以调整这些颜色，使您能够将" +"聊天集成到您的网站中，就像之前一样。" #: ../channels/chat.rst:51 msgid "Configuration of the Chat widget" -msgstr "" +msgstr "聊天小部件的配置" #: ../channels/chat.rst:53 msgid "" "You can create chat widgets for your web pages to allow visitors to chat " "with you." -msgstr "" +msgstr "您可以为您的网页创建聊天小部件，以便访问者与您聊天。" #: ../channels/chat.rst:56 msgid "" "The area for configuring the chat can be found in the admin area at Channels " "→ Chat:" -msgstr "" +msgstr "可以在管理员区域的Channels → Chat中找到配置聊天的区域：" #: ../channels/chat.rst:61 msgid "" @@ -152,10 +163,13 @@ msgid "" "Through the different previews you have the possibility to display directly " "how the presentation looks on different devices." msgstr "" +"您可以为不同的网站设置聊天，并独立编辑它们。集成的设计师可以帮助聊天小部件适" +"应网站的颜色。如果您不喜欢建议的设计，可以手动调整设计。通过不同的预览，您可" +"以直接显示在不同设备上的展示效果。" #: ../channels/chat.rst:69 msgid "**Usage**" -msgstr "" +msgstr "使用方法" #: ../channels/chat.rst:71 msgid "" @@ -163,45 +177,48 @@ msgid "" "the chat to be visible on. It should be placed at the end of the page's " "source code before the closing tag." msgstr "" +"将小部件代码插入到您希望聊天可见的每个页面的源代码中。它应该放在页面源代码的" +"末尾，位于关闭标签之前。" #: ../channels/chat.rst:77 msgid "**Result**" -msgstr "" +msgstr "结果" #: ../channels/chat.rst:79 msgid "The final result will look like the following:" -msgstr "" +msgstr "最终结果将如下所示：" #: ../channels/chat.rst:83 msgid "**Requirements**" -msgstr "" +msgstr "需求" #: ../channels/chat.rst:85 msgid "" "Zammad chat requires jQuery. If you don't already use it on your website " "include it like this:" -msgstr "" +msgstr "Zammad 聊天需要 jQuery。如果您的网站尚未使用它，请按照以下方式包含它：" #: ../channels/chat.rst:88 ../channels/form.rst:182 msgid "" "````" msgstr "" +"````" #: ../channels/chat.rst:90 msgid "You have two options to implement the chat on your website:" -msgstr "" +msgstr "您有两种方式在您的网站上实施聊天功能：" #: ../channels/chat.rst:92 msgid "Automatically show chat (that's the default-setting)" -msgstr "" +msgstr "自动显示聊天（这是默认设置）" #: ../channels/chat.rst:93 msgid "or manually open chat." -msgstr "" +msgstr "或者手动打开聊天。" #: ../channels/chat.rst:95 msgid "**Chat restrictions**" -msgstr "" +msgstr "**聊天限制**" #: ../channels/chat.rst:97 msgid "" @@ -210,78 +227,81 @@ msgid "" "block the wished IP addresses and countries fast and easily via the chat " "configuration in the admin panel. The configuration panel looks like this:" msgstr "" +"您为目标群体提供聊天服务，但您不想为某些IP地址或国家/地区激活聊天功能吗？那" +"么，您可以通过管理员面板中的聊天配置快速轻松地阻止所需的IP地址和国家。配置面" +"板如下所示：" #: ../channels/chat.rst:104 msgid "" "You can also find more information about the chat customization in the admin " "area." -msgstr "" +msgstr "您还可以在管理员区域中找到有关聊天自定义的更多信息。" #: ../channels/email/accounts.rst:2 ../channels/google/accounts.rst:2 #: ../channels/microsoft365/accounts.rst:2 msgid "Accounts" -msgstr "" +msgstr "账户" #: ../channels/email/accounts.rst:18 ../channels/google/accounts.rst:32 #: ../channels/microsoft365/accounts.rst:32 msgid ":doc:`accounts/account-setup`" -msgstr "" +msgstr ":doc:`accounts/account-setup`" #: ../channels/email/accounts.rst:13 msgid "Use the **New Email Account** dialog to connect your account." -msgstr "" +msgstr "使用**新建电子邮件账户**对话框来连接您的账户。" #: ../channels/email/accounts.rst:0 msgid "New Email Account dialog" -msgstr "" +msgstr "新建电子邮件账户对话框" #: ../channels/email/accounts.rst:27 ../channels/google/accounts.rst:50 #: ../channels/microsoft365/accounts.rst:50 msgid ":doc:`accounts/secondary-addresses`" -msgstr "" +msgstr ":doc:`accounts/secondary-addresses`" #: ../channels/email/accounts.rst:21 ../channels/google/accounts.rst:44 #: ../channels/microsoft365/accounts.rst:44 msgid "" "Send and receive email at **additional email addresses**, all through the " "same mailbox/account." -msgstr "" +msgstr "通过同一个邮箱/账户，在**额外的电子邮件地址**发送和接收邮件。" #: ../channels/email/accounts.rst:37 ../channels/google/accounts.rst:58 #: ../channels/microsoft365/accounts.rst:58 msgid ":doc:`accounts/managing-accounts`" -msgstr "" +msgstr ":doc:`accounts/managing-accounts`" #: ../channels/email/accounts.rst:30 ../channels/google/accounts.rst:53 #: ../channels/microsoft365/accounts.rst:53 msgid "Edit the configuration of existing accounts in the **Accounts Panel**." -msgstr "" +msgstr "在**账户面板**中编辑现有账户的配置。" #: ../channels/email/accounts.rst:0 #: ../channels/email/accounts/managing-accounts.rst:None #: ../channels/google/accounts.rst:0 ../channels/microsoft365/accounts.rst:0 msgid "Existing accounts can be edited from the Accounts panel." -msgstr "" +msgstr "可以从账户面板编辑现有的账户。" #: ../channels/email/accounts.rst:45 msgid ":doc:`accounts/email-notification`" -msgstr "" +msgstr ":doc:`accounts/email-notification`" #: ../channels/email/accounts.rst:40 msgid "" "Configure the outgoing mail provider for **system notifications**. (Self-" "hosted installations only.)" -msgstr "" +msgstr "为**系统通知**配置外发邮件提供商。（仅限自托管安装）" #: ../channels/email/accounts/account-setup.rst:2 #: ../channels/google/accounts/account-setup.rst:2 #: ../channels/microsoft365/accounts/account-setup.rst:2 msgid "Account Setup" -msgstr "" +msgstr "账户设置" #: ../channels/email/accounts/account-setup.rst:4 msgid "Setting up a new email account? Here’s what all the settings do." -msgstr "" +msgstr "设置新的电子邮件账户？以下是所有设置的功能。" #: ../channels/email/accounts/account-setup.rst:6 #: ../channels/google/accounts/account-setup.rst:8 @@ -289,20 +309,21 @@ msgstr "" msgid "" "☠️ **But first, a word of warning!** The import process does things you might " "not expect:" -msgstr "" +msgstr "☠️ **但首先，警告一下！**导入过程可能会做出您意想不到的事情：" #: ../channels/email/accounts/account-setup.rst:9 #: ../channels/google/accounts/account-setup.rst:11 #: ../channels/microsoft365/accounts/account-setup.rst:10 msgid "" "🚯 **Zammad will delete all emails in your inbox during the import process.**" -msgstr "" +msgstr "🚯 **在导入过程中，Zammad将删除您收件箱中的所有电子邮件。**" #: ../channels/email/accounts/account-setup.rst:12 msgid "" "Use the *Experts* dialog to :ref:`disable this behavior `." msgstr "" +"使用*专家*对话框来 :ref:`禁用此行为`。" #: ../channels/email/accounts/account-setup.rst:19 #: ../channels/google/accounts/account-setup.rst:17 @@ -311,16 +332,17 @@ msgid "" "📮 **Zammad will send an auto-reply message to every email it imports.** " "(Including the old ones!)" msgstr "" +"📮 **Zammad会对其导入的每封电子邮件发送自动回复消息。**（包括旧的电子邮件！）" #: ../channels/email/accounts/account-setup.rst:22 msgid "" "Use the *Experts* dialog to :ref:`change this behavior `." -msgstr "" +msgstr "使用*专家*对话框来 :ref:`更改此行为`。" #: ../channels/email/accounts/account-setup.rst:31 msgid "**Gmail / G Suite users:**" -msgstr "" +msgstr "**Gmail / G Suite用户：**" #: ../channels/email/accounts/account-setup.rst:28 msgid "" @@ -328,10 +350,13 @@ msgid "" "date, do **not** add your account as an email channel — instead, create a :" "doc:`Google channel `." msgstr "" +"Google正在升级其安全策略。为了保持最新状态，**不要**将您的账户添加为电子邮件" +"渠道 —— 而是创建一个 :doc:`Google渠道 `。" #: ../channels/email/accounts/account-setup.rst:36 msgid "**Microsoft 365 users:**" -msgstr "" +msgstr "**Microsoft 365用户：**" #: ../channels/email/accounts/account-setup.rst:34 msgid "" @@ -340,41 +365,46 @@ msgid "" "a :doc:`Microsoft 365 channel `." msgstr "" +"Microsoft正在升级其安全策略。为了保持最新状态，**不要**将您的帐户添加为电子邮" +"件渠道 —— 而是创建一个 :doc:`Microsoft 365渠道 `。" #: ../channels/email/accounts/account-setup.rst:40 msgid "Basic" -msgstr "" +msgstr "基础" #: ../channels/email/accounts/account-setup.rst:42 msgid "" "In most cases, Zammad is smart enough to figure out your email provider’s " "configuration based on your email address alone." msgstr "" +"在大多数情况下，Zammad只根据您的电子邮件地址就能智能地找出您的电子邮件提供商" +"的配置。" #: ../channels/email/accounts/account-setup.rst:None msgid "" "Enter your email address and password, and Zammad will figure out the\n" "rest." -msgstr "" +msgstr "输入您的电子邮件地址和密码，Zammad会自动处理剩下的部分。" #: ../channels/email/accounts/account-setup.rst:67 msgid "Organization & Department Name" -msgstr "" +msgstr "组织和部门名称" #: ../channels/email/accounts/account-setup.rst:53 #: ../channels/email/accounts/secondary-addresses.rst:22 msgid "The display name used for outgoing email." -msgstr "" +msgstr "用于发出电子邮件的显示名称。" #: ../channels/email/accounts/account-setup.rst:0 #: ../channels/email/accounts/secondary-addresses.rst:0 msgid "Screenshot of customer inbox with email from \"Chrispresso Sales\"" -msgstr "" +msgstr "显示来自“Chrispresso Sales”的客户收件箱的截图。" #: ../channels/email/accounts/account-setup.rst:60 #: ../channels/email/accounts/secondary-addresses.rst:29 msgid "A customer’s inbox with an auto-reply from **Chrispresso Sales**." -msgstr "" +msgstr "客户的收件箱中有来自**Chrispresso Sales**的自动回复。" #: ../channels/email/accounts/account-setup.rst:62 msgid "" @@ -382,6 +412,8 @@ msgid "" "account, you can define a separate Organization & Department Name for each " "one." msgstr "" +"如果您在一个账户中添加：doc:`多个地址`，您可以为每一个地" +"址定义一个单独的组织和部门名称。" #: ../channels/email/accounts/account-setup.rst:66 #: ../channels/email/accounts/secondary-addresses.rst:31 @@ -389,29 +421,35 @@ msgid "" "Email display names value can be :ref:`further customized in the Settings " "tab `." msgstr "" +"电子邮件显示名称的值可以在设置选项卡中进一步自定义：ref:``。" #: ../channels/email/accounts/account-setup.rst:77 #: ../channels/email/accounts/secondary-addresses.rst:35 #: ../channels/email/index.rst:2 ../channels/form.rst:20 #: ../manage/groups/settings.rst:67 ../system/objects/types.rst:125 msgid "Email" -msgstr "" +msgstr "Email" #: ../channels/email/accounts/account-setup.rst:70 msgid "Your email address." -msgstr "" +msgstr "您的电子邮件地址。" #: ../channels/email/accounts/account-setup.rst:72 msgid "" "If your account login/username is different from your email address, use the " "*Experts* dialog (see below)." msgstr "" +"如果您的账户登录名/用户名与您的电子邮件地址不同，请使用*专家*对话框（见下" +"文）。" #: ../channels/email/accounts/account-setup.rst:75 msgid "" "If your inbox receives mail for more than one email address, be sure to :doc:" "`add your alternate addresses ` after account setup." msgstr "" +"如果您的收件箱接收多个电子邮件地址的邮件，请确保在设置账户后 :doc:`添加您的备" +"用地址 `。" #: ../channels/email/accounts/account-setup.rst:80 #: ../channels/email/accounts/account-setup.rst:127 @@ -419,60 +457,62 @@ msgstr "" #: ../channels/email/accounts/email-notification.rst:33 #: ../settings/security/password.rst:2 msgid "Password" -msgstr "" +msgstr "密码" #: ../channels/email/accounts/account-setup.rst:80 #: ../channels/email/accounts/account-setup.rst:127 #: ../channels/email/accounts/account-setup.rst:246 #: ../channels/email/accounts/email-notification.rst:33 msgid "Your account password." -msgstr "" +msgstr "您的账户密码。" #: ../channels/email/accounts/account-setup.rst:87 #: ../channels/email/accounts/managing-accounts.rst:26 msgid "Destination Group" -msgstr "" +msgstr "目标群组" #: ../channels/email/accounts/account-setup.rst:83 msgid "" "The :doc:`group ` that incoming mail will be assigned " "to." -msgstr "" +msgstr "接收邮件将被分配到的 :doc:`群组 `。" #: ../channels/email/accounts/account-setup.rst:86 msgid "" "Use :doc:`filters ` for more fine-grained sorting " "of incoming email." -msgstr "" +msgstr "使用 :doc:`过滤器 ` 来进行更精细的收件排序。" #: ../channels/email/accounts/account-setup.rst:92 msgid "Experts" -msgstr "" +msgstr "专家" #: ../channels/email/accounts/account-setup.rst:94 msgid "" "If Zammad can’t figure out how to connect your account (or if you just want " "to access advanced settings), use the *Experts* dialog." msgstr "" +"如果 Zammad 无法确定如何连接您的帐户（或者您只是想访问高级设置），请使用 *专" +"家* 对话框。" #: ../channels/email/accounts/account-setup.rst:None msgid "" "When auto-detection fails, you will be presented with the \"Experts\"\n" "account setup dialog." -msgstr "" +msgstr "当自动检测失败时，将会显示“专家”账户设置对话框。" #: ../channels/email/accounts/account-setup.rst:105 msgid "Email Inbound" -msgstr "" +msgstr "电子邮件入站" #: ../channels/email/accounts/account-setup.rst:113 #: ../system/objects/types.rst:128 msgid "Type" -msgstr "" +msgstr "类型" #: ../channels/email/accounts/account-setup.rst:108 msgid "Choose from **IMAP** and **POP3**." -msgstr "" +msgstr "从**IMAP**和**POP3**中选择。" #: ../channels/email/accounts/account-setup.rst:110 msgid "" @@ -480,22 +520,24 @@ msgid "" "messages on the server ` or :ref:" "`specify which folder to fetch from `.)" msgstr "" +"在大多数情况下，你会选择IMAP。（使用POP3，你将无法在服务器上保留消息或指定要" +"从哪个文件夹获取消息。）" #: ../channels/email/accounts/account-setup.rst:118 #: ../channels/email/accounts/account-setup.rst:238 #: ../channels/email/accounts/email-notification.rst:24 msgid "Host" -msgstr "" +msgstr "主机" #: ../channels/email/accounts/account-setup.rst:116 msgid "" "Your email server’s hostname or IP address (*e.g.,* ``imap.gmail.com``)." -msgstr "" +msgstr "你的电子邮件服务器的主机名或IP地址（例如，``imap.gmail.com``）。" #: ../channels/email/accounts/account-setup.rst:118 #: ../channels/email/accounts/account-setup.rst:149 msgid "Contact your email provider or system administrator if you don’t know." -msgstr "" +msgstr "如果你不知道，请联系你的电子邮件提供商或系统管理员。" #: ../channels/email/accounts/account-setup.rst:124 #: ../channels/email/accounts/account-setup.rst:243 @@ -503,25 +545,30 @@ msgstr "" #: ../settings/security/third-party/microsoft.rst:72 #: ../system/objects/permissions.rst:53 ../system/sessions.rst:23 msgid "User" -msgstr "" +msgstr "用户" #: ../channels/email/accounts/account-setup.rst:121 msgid "" "This field is being pre-filled with your email address in case you've " "provided one before opening the expert settings." msgstr "" +"如果你在打开专家设置之前提供了电子邮件地址，那么这个字段将会预先填充你的电子" +"邮件地址。" #: ../channels/email/accounts/account-setup.rst:124 msgid "Adjust this setting in case your username and email address differ." -msgstr "" +msgstr "如果你的用户名和电子邮件地址不同，请调整此设置。" #: ../channels/email/accounts/account-setup.rst:144 msgid "SSL / STARTTLS" msgstr "" +"SSL / STARTTLS是两种加密连接协议，用于保护网络传输数据的安全。SSL是Secure " +"Sockets Layer的缩写，意为安全套接层；STARTTLS则是一种协议命令，用于将一个未加" +"密的连接升级为加密连接。" #: ../channels/email/accounts/account-setup.rst:130 msgid "Enable encryption when fetching messages." -msgstr "" +msgstr "在获取消息时启用加密。" #: ../channels/email/accounts/account-setup.rst:132 msgid "You can choose from the following options:" @@ -2739,7 +2786,7 @@ msgstr "" #: ../channels/form.rst:234 ../manage/public-links.rst:61 #: ../system/subscription/billing.rst:57 msgid "Description" -msgstr "" +msgstr "描述" #: ../channels/form.rst:235 msgid "``form_ticket_create_by_ip_per_hour``" @@ -3966,6 +4013,210 @@ msgid "" "Contact your administrator if you don’t have access to an admin account." msgstr "" +#: ../channels/microsoft365/common-errors.rst:2 +msgid "Common errors" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:4 +msgid "" +"Here you can find some common errors in M365 context. Also have a look at " +"the general :doc:`M365 documentation ` for the " +"configuration." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:9 +msgid "Incorrect client ID" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:11 +msgid "" +"**Error message:** AADSTS00016: Application with identifier 'xxxxxxxx' was " +"not found in the directory 'MSFT'. This can happen if the application has " +"not been installed by the administrator of the tenant or consented to by any " +"user in the tenant. You may have sent your authentication request to the " +"wrong tenant." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:None +#: ../channels/microsoft365/common-errors.rst:104 +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:22 +msgid "" +"In this case, please compare whether the client ID created in Zammad matches " +"that in Azure for the Azure App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:25 +msgid "" +"The Client ID can be found in Zammad under Settings > Channels > Microsoft " +"365 > App Configuration. See :doc:`here ` " +"how to find the client ID in Azure and where to copy it to in Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:31 +msgid "Wrong or expired client secret" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:33 +msgid "**Error message:** 500: We're sorry, but something went wrong." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:40 +msgid "" +"This error occurs when the client uses an incorrect or expired client secret." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:42 +msgid "" +"**Important notice:** We never ask the client for the client secret as this " +"can potentially be a security risk. We ask the customer to create a new " +"client secret and copy the value and not the ID to Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:47 +msgid "See :doc:`here ` for more information." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:50 +msgid "Wrong tenant" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:52 +msgid "" +"**Error message:** AADSTS0023: Specified tenant identifier 'xxxxxxxx' is " +"neither a valid DNS name, nor a valid external domain." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:60 +msgid "" +"If a wrong tenant is used in Zammad or the email account is not a member of " +"the tenant created in Zammad, this error message occurs." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:63 +msgid "" +"In this case, please check if the tenant is entered correctly in Zammad, or " +"remove the tenant completely." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:66 +msgid "" +"**Important notice:** Once the tenant is completely removed, all email " +"accounts can be created in Zammad regardless of which tenant the email " +"account is a member of." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:71 +msgid "Request admin consent" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:73 +msgid "**Prompt:** approval required" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:80 +msgid "" +"This message occurs when the admin tries to create an email account in " +"Zammad that has not yet received approval from the Azure global admin." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:83 +msgid "" +"In our documentation, :doc:`step-by-step instructions ` can be found on how to request admin " +"consent from Zammad." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:88 +msgid "" +"The request for the admin consent can be bypassed by assigning the admin " +"consent in Azure to the App." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:91 +msgid "" +"Home > App Registration > Manage > API Permission > Grant admin consent for " +"\"MSFT\"." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:95 +msgid "Missing permissions for the Azure user" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:97 +msgid "" +"**Error message:** Can't use Channel:Driver::SMTPAuthentificationError:Net::" +"SMTPAuthentificationError" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:104 +msgid "Error message in the M365 channel settings" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:106 +msgid "or" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:113 +msgid "Error message in the ticket" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:115 +msgid "" +"This error occurs when the admin wants to create an email account in Zammad " +"whose user does not have permission for SMTP authentication to the mail " +"server. Please check the following two most common problems in this case." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:121 +msgid "Private email account" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:123 +msgid "" +"If it is a private email account, the admin must grant the SMTP " +"authentication permission to the user of the inbox. The permission is " +"provided at https://admin.microsoft.com." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:127 +msgid "" +"Add the SMTP authentication permission under Users > Active Users > click on " +"the User > Email > Manage Email Apps." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:137 +msgid "Shared inbox" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:139 +msgid "" +"If it is a shared inbox, you can try to enable the SMTP Authentication " +"(``SmtpClientAuthenticationDisabled``) in the Azure shell. This isn't a " +"Zammad problem, so we can only help to a limited extent here." +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:143 +msgid "To enable the SMTP Authentication, use the following commands:" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:145 +msgid "If not installed::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:149 +msgid "Log in to Exchange using Powershell::" +msgstr "" + +#: ../channels/microsoft365/common-errors.rst:153 +msgid "" +"Switching on the SMTP authentication for a mailbox - also possible with a " +"shared mailbox::" +msgstr "" + #: ../channels/microsoft365/email-headers.rst:3 msgid "" "Email header manipulation in Microsoft 365 channels work **just like in " @@ -3991,29 +4242,37 @@ msgstr "" msgid "Microsoft 365" msgstr "" -#: ../channels/microsoft365/index.rst:13 +#: ../channels/microsoft365/index.rst:14 msgid "Connect a Microsoft 365 account (formerly “Office 365”) to Zammad." msgstr "" -#: ../channels/microsoft365/index.rst:19 +#: ../channels/microsoft365/index.rst:20 msgid "" "Microsoft 365 channels are a specialized kind of :doc:`📨 email channel `." msgstr "" -#: ../channels/microsoft365/index.rst:22 +#: ../channels/microsoft365/index.rst:23 msgid "" "This documentation part does not cover :doc:`🗝 user authentication `." msgstr "" -#: ../channels/microsoft365/index.rst:25 +#: ../channels/microsoft365/index.rst:26 msgid "" "If you’re already familiar with email channels, you can skip most of this—" "but **watch out for the “Accounts” section**, which has a few extra quirks " "due to Microsoft’s strict security measures." msgstr "" +#: ../channels/microsoft365/index.rst:34 +msgid ":doc:`🛟 Common M365 errors `" +msgstr "" + +#: ../channels/microsoft365/index.rst:35 +msgid "Here you can find common errors and how to fix them." +msgstr "" + #: ../channels/microsoft365/settings.rst:3 msgid "" "Settings in Microsoft 365 channels are **just like settings in email " @@ -4158,267 +4417,376 @@ msgstr "" msgid "The message will appear in your Telegram client." msgstr "" -#: ../channels/twitter.rst:2 ../settings/security/third-party/twitter.rst:2 -msgid "Twitter" +#: ../channels/twitter-x/twitter.rst:2 +msgid "Twitter/X" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:6 +msgid "*Updated: 08/2023*" +msgstr "" + +#: ../channels/twitter-x/twitter.rst:8 +msgid "" +"Please note: Currently, we keep naming it \"Twitter\" or \"Twitter/X\" in " +"the documentation, as it is the quite common name and for better " +"readability. Of course we mean just \"X\"." +msgstr "" + +#: ../channels/twitter-x/twitter.rst:12 +msgid "" +"⚠️ Due to the current situation, there are some issues regarding the Twitter/" +"X integration. Please see :doc:`twitter-x-note` for further details before " +"reading on!" msgstr "" -#: ../channels/twitter.rst:4 +#: ../channels/twitter-x/twitter.rst:16 msgid "" "Zammad supports Twitter integration, meaning you can send and receive tweets " "and DMs just like emails!" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "Twitter Ticket with draft reply" msgstr "" -#: ../channels/twitter.rst:11 +#: ../channels/twitter-x/twitter.rst:23 msgid "" "Twitter tickets will show a 🐦 Twitter bird in the reply area. Just click on " "the reply button (as you would for an email) to tweet back." msgstr "" -#: ../channels/twitter.rst:15 +#: ../channels/twitter-x/twitter.rst:27 msgid "To set it up, follow the steps below:" msgstr "" -#: ../channels/twitter.rst:17 +#: ../channels/twitter-x/twitter.rst:29 msgid "Apply for a `Twitter Developer account`_." msgstr "" -#: ../channels/twitter.rst:18 +#: ../channels/twitter-x/twitter.rst:30 msgid "`Create a new Twitter app`_ for Zammad." msgstr "" -#: ../channels/twitter.rst:19 +#: ../channels/twitter-x/twitter.rst:31 msgid "" "Set your new app’s permissions to *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:21 +#: ../channels/twitter-x/twitter.rst:33 msgid "Generate a new access token & secret." msgstr "" -#: ../channels/twitter.rst:22 +#: ../channels/twitter-x/twitter.rst:34 msgid "`Set up a dev environment`_ for the Account Activity API." msgstr "" -#: ../channels/twitter.rst:23 +#: ../channels/twitter-x/twitter.rst:35 msgid "Add your new Twitter app in Zammad." msgstr "" -#: ../channels/twitter.rst:24 +#: ../channels/twitter-x/twitter.rst:36 msgid "Add your Twitter account in Zammad." msgstr "" -#: ../channels/twitter.rst:25 +#: ../channels/twitter-x/twitter.rst:37 msgid "" "Configure filters for creating new tickets based on **#tags** and " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:28 +#: ../channels/twitter-x/twitter.rst:40 msgid "Read on for details about each step." msgstr "" -#: ../channels/twitter.rst:31 +#: ../channels/twitter-x/twitter.rst:43 msgid "1. Apply for a Twitter Developer account" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "Twitter Developer account: Welcome page" msgstr "" -#: ../channels/twitter.rst:37 +#: ../channels/twitter-x/twitter.rst:49 msgid "" "This welcome page is displayed after completing the application for a " "Developer account." msgstr "" -#: ../channels/twitter.rst:40 +#: ../channels/twitter-x/twitter.rst:52 msgid "" "You will need a regular Twitter account with a verified phone number to " "apply for a `Twitter Developer account`_ (at https://developer.twitter.com)." msgstr "" -#: ../channels/twitter.rst:43 +#: ../channels/twitter-x/twitter.rst:55 msgid "" "During the application process, you will be asked to **Describe in your own " "words what you are building**. You may use the answer below::" msgstr "" -#: ../channels/twitter.rst:55 +#: ../channels/twitter-x/twitter.rst:67 msgid "2. Create a new Twitter app for Zammad" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "Twitter Developer account: Create app page" msgstr "" -#: ../channels/twitter.rst:61 +#: ../channels/twitter-x/twitter.rst:73 msgid "" "To create a new app, select **Apps** under your user menu, then click " "**Create an app**." msgstr "" -#: ../channels/twitter.rst:64 +#: ../channels/twitter-x/twitter.rst:76 msgid "" "Once you have finished setting up your Developer account, use it to `create " "a new Twitter app`_. The following fields are **required:**" msgstr "" -#: ../channels/twitter.rst:70 +#: ../channels/twitter-x/twitter.rst:82 msgid "App name" msgstr "" -#: ../channels/twitter.rst:69 +#: ../channels/twitter-x/twitter.rst:81 msgid "" "Must be unique *across all of Twitter.* No other developer account may " "create an app with the same name." msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Application description" msgstr "" -#: ../channels/twitter.rst:73 +#: ../channels/twitter-x/twitter.rst:85 msgid "Anything is fine here." msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "Website URL" msgstr "" -#: ../channels/twitter.rst:76 +#: ../channels/twitter-x/twitter.rst:88 msgid "The URL of your Zammad instance." msgstr "" -#: ../channels/twitter.rst:82 +#: ../channels/twitter-x/twitter.rst:94 msgid "Callback URLs" msgstr "" -#: ../channels/twitter.rst:79 +#: ../channels/twitter-x/twitter.rst:91 msgid "" "``https:///api/v1/external_credentials/twitter/callback``" msgstr "" -#: ../channels/twitter.rst:81 +#: ../channels/twitter-x/twitter.rst:93 msgid "" "This URL is also visible in the **Connect Twitter App** dialog of your " "Zammad admin settings panel." msgstr "" -#: ../channels/twitter.rst:88 +#: ../channels/twitter-x/twitter.rst:100 msgid "Tell us how this app will be used" msgstr "" -#: ../channels/twitter.rst:85 +#: ../channels/twitter-x/twitter.rst:97 msgid "Anything is fine here. We suggest the following::" msgstr "" -#: ../channels/twitter.rst:91 +#: ../channels/twitter-x/twitter.rst:103 msgid "3. Set your new app’s permissions" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App permissions page" msgstr "" -#: ../channels/twitter.rst:97 +#: ../channels/twitter-x/twitter.rst:109 msgid "Select *Read, write, and access direct messages.*" msgstr "" -#: ../channels/twitter.rst:100 +#: ../channels/twitter-x/twitter.rst:112 msgid "4. Generate a new access token & secret" msgstr "" -#: ../channels/twitter.rst:0 +#: ../channels/twitter-x/twitter.rst:0 msgid "Twitter Developer account: App keys and tokens page" msgstr "" -#: ../channels/twitter.rst:106 +#: ../channels/twitter-x/twitter.rst:118 msgid "You will need all four keys/tokens later, so don’t close this tab." msgstr "" -#: ../channels/twitter.rst:109 +#: ../channels/twitter-x/twitter.rst:121 msgid "5. Set up a dev environment" msgstr "" -#: ../channels/twitter.rst:111 +#: ../channels/twitter-x/twitter.rst:123 msgid "" "After creating your app, `set up a dev environment`_ for the Account " "Activity API." msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "Twitter Developer account: Dev environments page" msgstr "" -#: ../channels/twitter.rst:118 +#: ../channels/twitter-x/twitter.rst:130 msgid "" "Name it whatever you like (*e.g.,* ``zammad``). You will need the label " "later, so don’t forget it." msgstr "" -#: ../channels/twitter.rst:122 +#: ../channels/twitter-x/twitter.rst:134 msgid "6. Add your new Twitter app in Zammad" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "Zammad: Configure Twitter app" msgstr "" -#: ../channels/twitter.rst:128 +#: ../channels/twitter-x/twitter.rst:140 msgid "" "Add your new Twitter app under **Channels > Twitter** in the admin settings " "panel. You will need the keys, tokens, and dev environment label from Steps " "4 and 5." msgstr "" -#: ../channels/twitter.rst:133 +#: ../channels/twitter-x/twitter.rst:145 msgid "7. Add your Twitter account in Zammad" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "Zammad: Add Twitter account" msgstr "" -#: ../channels/twitter.rst:139 +#: ../channels/twitter-x/twitter.rst:151 msgid "" "Click **Add Account** under **Channels > Twitter** in the admin settings " "panel." msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "Twitter: Authorize Zammad" msgstr "" -#: ../channels/twitter.rst:146 +#: ../channels/twitter-x/twitter.rst:158 msgid "" "You will be redirected to Twitter and asked to authorize Zammad to access " "your account." msgstr "" -#: ../channels/twitter.rst:150 +#: ../channels/twitter-x/twitter.rst:162 msgid "8. Configure filters" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "Zammad: Configure Twitter accounts" msgstr "" -#: ../channels/twitter.rst:156 +#: ../channels/twitter-x/twitter.rst:168 msgid "" "Set up filters to automatically create new tickets based on **#tags** or " "**@mentions**." msgstr "" -#: ../channels/twitter.rst:159 +#: ../channels/twitter-x/twitter.rst:171 msgid "" "That’s it! Now, incoming tweets and DMs will be automatically turned into " "Zammad tickets." msgstr "" +#: ../channels/twitter-x/twitter-x-note.rst:4 +msgid "Twitter/X note" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:5 +msgid "Updated: 08/2023" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:8 +msgid "Baseline situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:10 +msgid "" +"The Twitter integration implemented in Zammad provides the following " +"functionalities:" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:13 +msgid "" +"Search for definable terms and automatic ticket creation based on the results" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:15 +msgid "" +"Live notifications for your own Twitter account (e.g. if you are mentioned " +"in a tweet or receive direct messages), that will be transformed into tickets" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:19 +msgid "Current situation" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:21 +msgid "" +"The adjustments made to the API at Twitter/X (introduction of v2) as well as " +"the restructuring of the access levels/pricing models (Free, Basic, Pro - " +"https://developer.twitter.com/en/products/twitter-api) mean that the above-" +"mentioned functionalities are no longer available in connection with old " +"\"app registrations\" at the present time. These changes are heavily " +"discussed in the Twitter community and cause discomfort." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:28 +msgid "" +"In addition, we don't know if there will be another change on the part of " +"Twitter/X in the future that will further limit or even restore " +"functionality." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:32 +msgid "Prerequisite for the continued operation of Twitter in Zammad" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:34 +msgid "" +"Access to the \"old\" Twitter API v1.1 or the Account Activity API, which is " +"required for our functionalities, is now only available at the \"Enterprise" +"\" access level. According to Twitter, the monthly costs for this start at " +"42,000 USD." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:40 +msgid "Future" +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:42 +msgid "" +"We sincerely regret the current situation, but unfortunately our hands are " +"tied. If there are no more changes to the Twitter API or access levels, we " +"will consider removing the Twitter integration with Zammad 7.0. At the " +"moment, we are also in the process of monitoring the market very closely to " +"see if there are any alternatives to Twitter/X that we can integrate into " +"Zammad, and if so, which ones." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:49 +msgid "As soon as we have news about this, we will inform you." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:51 +msgid "" +"We understand that this news is unsatisfactory for you and would have " +"preferred more positive news. However, we would like to play with open cards " +"at this point and provide clarity." +msgstr "" + +#: ../channels/twitter-x/twitter-x-note.rst:55 +msgid "⬅️ :doc:`Back to Twitter/X Channel <./twitter>`." +msgstr "" + #: ../channels/web.rst:2 msgid "Web" msgstr "" @@ -5698,15 +6066,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 ../manage/users/index.rst:17 +#: ../manage/organizations/index.rst:16 msgid "via REST API" msgstr "" @@ -5794,7 +6162,7 @@ msgstr "" msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:57 +#: ../manage/organizations/index.rst:61 ../manage/users/index.rst:60 msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" msgstr "" @@ -5889,11 +6257,11 @@ msgid "" "assignments." msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:136 +#: ../manage/organizations/index.rst:124 ../manage/users/index.rst:139 msgid "Notes are visible to all staff members, **including agents**." msgstr "" @@ -5907,11 +6275,11 @@ msgstr "" msgid "Wish you could add your own fields to the New/Edit Organization dialog?" msgstr "" -#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:143 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:146 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:164 +#: ../manage/organizations/index.rst:146 ../manage/users/index.rst:167 msgid "▶️ Active" msgstr "" @@ -6820,7 +7188,7 @@ msgid "``admin.channel_twitter``" msgstr "" #: ../manage/roles/admin-permissions.rst:82 -msgid ":doc:`Channels > Twitter `" +msgid ":doc:`Channels > Twitter `" msgstr "" #: ../manage/roles/admin-permissions.rst:84 @@ -9371,14 +9739,6 @@ msgid "" "notification emails in German." msgstr "" -#: ../manage/users/index.rst:17 -msgid "via LDAP/Active Directory integration" -msgstr "" - -#: ../manage/users/index.rst:17 -msgid "via Exchange integration" -msgstr "" - #: ../manage/users/index.rst:2 msgid "Users" msgstr "" @@ -9394,67 +9754,89 @@ msgstr "" msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:15 +#: ../manage/users/index.rst:20 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:26 +#: ../manage/users/index.rst:16 +msgid ":doc:`via the Admin Panel `" +msgstr "" + +#: ../manage/users/index.rst:17 +msgid ":doc:`via CSV import `" +msgstr "" + +#: ../manage/users/index.rst:18 +msgid "" +":doc:`via LDAP/Active Directory integration `" +msgstr "" + +#: ../manage/users/index.rst:19 +msgid ":doc:`via Exchange integration `" +msgstr "" + +#: ../manage/users/index.rst:20 +msgid "`via REST API `_" +msgstr "" + +#: ../manage/users/index.rst:29 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:28 +#: ../manage/users/index.rst:31 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:34 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:33 +#: ../manage/users/index.rst:36 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " "monitors, and if it doesn’t recognize the address, ✨ **poof**—new customer " "account!" msgstr "" -#: ../manage/users/index.rst:38 +#: ../manage/users/index.rst:41 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:45 +#: ../manage/users/index.rst:48 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:47 +#: ../manage/users/index.rst:50 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren’t are described below." msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:55 +#: ../manage/users/index.rst:58 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:59 +#: ../manage/users/index.rst:62 msgid "" "In most cases, agents can, too (using the `new ticket dialog`_, `search " "bar`_ or the `ticket pane`_)." msgstr "" -#: ../manage/users/index.rst:85 +#: ../manage/users/index.rst:88 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:70 +#: ../manage/users/index.rst:73 msgid "" "A user’s email and login may differ, but **either one can be used to sign in." "**" @@ -9464,13 +9846,13 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:79 +#: ../manage/users/index.rst:82 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:82 +#: ../manage/users/index.rst:85 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the " "`Zammad console `_, " @@ -9478,25 +9860,25 @@ msgid "" "`CSV import `." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:91 msgid "" "Yes, administrators really do have the power to change other users’ " "passwords." msgstr "" -#: ../manage/users/index.rst:90 +#: ../manage/users/index.rst:93 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:93 +#: ../manage/users/index.rst:96 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -9504,52 +9886,52 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:98 +#: ../manage/users/index.rst:101 msgid "" "🚫 **You can’t assign a customer to an organization that doesn’t exist yet.**" msgstr "" -#: ../manage/users/index.rst:101 +#: ../manage/users/index.rst:104 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:104 +#: ../manage/users/index.rst:107 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:107 +#: ../manage/users/index.rst:110 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:112 +#: ../manage/users/index.rst:115 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:117 +#: ../manage/users/index.rst:120 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:120 +#: ../manage/users/index.rst:123 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "👑 VIP" msgstr "" -#: ../manage/users/index.rst:123 +#: ../manage/users/index.rst:126 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -9561,39 +9943,39 @@ msgstr "" msgid "Ticket view showing a VIP user’s avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:133 +#: ../manage/users/index.rst:136 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:138 +#: ../manage/users/index.rst:141 msgid "" "😵 **Are you using the Note field to keep track of your own “custom” user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:144 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:146 +#: ../manage/users/index.rst:149 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what’s the " "difference?" msgstr "" -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:152 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:155 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:155 +#: ../manage/users/index.rst:158 msgid "Inactive users still appear in search results:" msgstr "" @@ -9601,29 +9983,29 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:161 +#: ../manage/users/index.rst:164 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " "users are greyed out." msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "🔓 Permissions" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:170 msgid "" "Under this heading, you can manage two separate (but related) user details:" msgstr "" -#: ../manage/users/index.rst:169 +#: ../manage/users/index.rst:172 msgid "" ":doc:`/manage/roles/index` dictate what users can do in the system. If you " "need to grant someone privileges to edit the knowledge base or access part " "of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:173 +#: ../manage/users/index.rst:176 msgid "" ":doc:`/manage/groups/access-levels` dictate which tickets an agent can work " "with. If someone’s not receiving notifications for incoming tickets or can’t " @@ -9634,18 +10016,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:187 msgid "" "**Top:** A user’s roles decide what kinds of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:191 msgid "**🤔 Huh? I don’t see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:193 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13733,6 +14115,10 @@ msgid "" "Have you double-checked your IdP’s user attribute mapping configuration?" msgstr "" +#: ../settings/security/third-party/twitter.rst:2 +msgid "Twitter" +msgstr "" + #: ../settings/security/third-party/twitter.rst:4 msgid "" "It is possible to create a quick login for your helpdesk via Twitter to do " @@ -15492,7 +15878,7 @@ msgstr "" #: ../system/integrations/checkmk/api-reference.rst:13 msgid "Example" -msgstr "" +msgstr "例如" #: ../system/integrations/checkmk/api-reference.rst:15 msgid "" @@ -15685,7 +16071,7 @@ msgstr "" #: ../system/integrations/checkmk/api-reference.rst:137 msgid "group" -msgstr "" +msgstr "组" #: ../system/integrations/checkmk/api-reference.rst:138 #: ../system/integrations/checkmk/api-reference.rst:172 @@ -15694,11 +16080,11 @@ msgstr "" #: ../system/integrations/checkmk/api-reference.rst:139 msgid "state" -msgstr "" +msgstr "状态" #: ../system/integrations/checkmk/api-reference.rst:140 msgid "priority" -msgstr "" +msgstr "优先级" #: ../system/integrations/checkmk/api-reference.rst:142 msgid "" @@ -18878,7 +19264,7 @@ msgid ":doc:`/channels/telegram` (incoming)" msgstr "" #: ../system/objects/permissions.rst:31 -msgid ":doc:`/channels/twitter` (incoming)" +msgid ":doc:`/channels/twitter-x/twitter` (incoming)" msgstr "" #: ../system/objects/permissions.rst:32 @@ -21753,4 +22139,4 @@ msgstr "" #: ../system/version.rst:4 msgid "Shows which version is currently being used on your Zammad-instance." -msgstr "" +msgstr "显示当前在您的Zammad实例上使用的版本。"