admin-docs.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2012 - 2023, Zammad Foundation
# This file is distributed under the same license as the Zammad package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: Zammad\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-02-28 13:09+0100\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 ../misc/first-steps.rst:88
msgid "Chat"
msgstr ""

#: ../channels/chat.rst:5 ../channels/facebook.rst:5
#: ../misc/object-conditions/basics.rst:5
#: ../settings/security/ssl-certificates.rst:5
#: ../settings/security/third-party/saml.rst:5
#: ../system/integrations/pgp/index.rst:5 ../system/objects/permissions.rst:5
msgid "Introduction"
msgstr ""

#: ../channels/chat.rst:7
msgid ""
"The chat feature in Zammad allows visitors of your website to initiate chats "
"with agents. You can find the settings in the admin panel under \"Channels\"."
msgstr ""

#: ../channels/chat.rst:10
msgid ""
"The feature is built to assist for proper customer support. And this is how "
"it works:"
msgstr ""

#: ../channels/chat.rst:13
msgid ""
"The chat widget will only be displayed to customers, if at least one agent "
"is available and has capacity."
msgstr ""

#: ../channels/chat.rst:15
msgid ""
"Agents can define how many simultaneous chat sessions they want to accept."
msgstr ""

#: ../channels/chat.rst:16
msgid ""
"An agent is set to inactive, if the agent doesn't accept new chat requests "
"or is offline. Because of this, your agents can take breaks without having "
"your customers to wait."
msgstr ""

#: ../channels/chat.rst:19
msgid ""
"You can define different topics for chats and agents can select for which "
"topic they want to accept chat sessions."
msgstr ""

#: ../channels/chat.rst:21
msgid "No automatic answer is send to the customer."
msgstr ""

#: ../channels/chat.rst:22
msgid ""
"Zammad sends an auto response as soon as the agents accepts the chat "
"request. This message is configurable by each agent individually."
msgstr ""

#: ../channels/chat.rst:24
msgid ""
"Zammad will try to adapt your main website colors to the chat. You can also "
"adjust the colors to customize it to your corporate design."
msgstr ""

#: ../channels/chat.rst:28 ../channels/microsoft365-graph/accounts.rst:17
#: ../misc/first-steps.rst:20 ../system/integrations/clearbit.rst:31
msgid "Configuration"
msgstr ""

#: ../channels/chat.rst:31 ../manage/checklist.rst:5
#: ../misc/object-conditions/basics.rst:433 ../system/monitoring.rst:9
msgid "General"
msgstr ""

#: ../channels/chat.rst:33
msgid ""
"The area for configuring the chat can be found in the admin panel under "
"**Channels > Chat**."
msgstr ""

#: ../channels/chat.rst:36
msgid ""
"You can set up chats for different websites and edit them independently. Use "
"the \"Topics\" function if you need a separation or you have specialized "
"agents for different topics. Your agents can choose then for which topic "
"they want to accept chats."
msgstr ""

#: ../channels/chat.rst:43
msgid ""
"The integrated designer helps the chat widget to adapt to the website color. "
"Zammad tries to fetch your website based on your FQDN. If this fails or you "
"want to override the preview, you can enter a URL manually and click on "
"load. You can get a preview for different devices by selecting the different "
"preview modes."
msgstr ""

#: ../channels/chat.rst:49
msgid ""
"If you don't like the proposed design, you can manually adjust it. Adjust "
"the color and apply a flat design if needed."
msgstr ""

#: ../channels/chat.rst:55
msgid "Chat Restrictions"
msgstr ""

#: ../channels/chat.rst:57
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:64
msgid ""
"You can also find more information about the chat customization in the admin "
"area."
msgstr ""

#: ../channels/chat.rst:68
msgid "Website Implementation"
msgstr ""

#: ../channels/chat.rst:71 ../channels/form.rst:156
#: ../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/chat.rst:73
msgid ""
"Zammad chat comes in two flavors: a version with and without jQuery. You can "
"choose which one you prefer by toggling the **With jQuery** switch that will "
"display the appropriate code snippet below."
msgstr ""

#: ../channels/chat.rst:77
msgid ""
"For jQuery version, if you don't already use it on your website, make sure "
"to first include it like this:"
msgstr ""

#: ../channels/chat.rst:85 ../manage/checklist.rst:16
#: ../system/integrations/smime/index.rst:41
msgid "Usage"
msgstr ""

#: ../channels/chat.rst:87
msgid "You have two options to implement the chat on your website:"
msgstr ""

#: ../channels/chat.rst:89
msgid "Automatically show the chat (that's the default setting)"
msgstr ""

#: ../channels/chat.rst:90
msgid "or manually open the chat."
msgstr ""

#: ../channels/chat.rst:92
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 ``</body>`` closing tag."
msgstr ""

#: ../channels/chat.rst:99
msgid "Result"
msgstr ""

#: ../channels/chat.rst:101
msgid "The final result will look like the following:"
msgstr ""

#: ../channels/email/accounts.rst:2
#: ../channels/microsoft365-graph/accounts.rst:2
#: ../channels/microsoft365/accounts.rst:2
msgid "Accounts"
msgstr ""

#: ../channels/email/accounts.rst:18 ../channels/microsoft365/accounts.rst:25
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/microsoft365/accounts.rst:34
msgid ":doc:`accounts/secondary-addresses`"
msgstr ""

#: ../channels/email/accounts.rst:21 ../channels/microsoft365/accounts.rst:33
msgid ""
"Send and receive email at **additional email addresses**, all through the "
"same mailbox/account."
msgstr ""

#: ../channels/email/accounts.rst:0
msgid "Add email address dialog"
msgstr ""

#: ../channels/email/accounts.rst:37 ../channels/microsoft365/accounts.rst:37
msgid ":doc:`accounts/managing-accounts`"
msgstr ""

#: ../channels/email/accounts.rst:30 ../channels/microsoft365/accounts.rst:37
msgid "Edit the configuration of existing accounts in the **Accounts Panel**."
msgstr ""

#: ../channels/email/accounts.rst:0
#: ../channels/email/accounts/managing-accounts.rst:None
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/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/basic-setup.rst:118
#: ../channels/microsoft365/accounts/account-setup.rst:8
msgid ""
"☠️ **But first, a word of warning!** The import process does things you might "
"not expect:"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:13
msgid ""
"By default, Zammad will **delete all emails** in your inbox during the "
"import process. Use the *Experts* dialog to :ref:`disable this behavior "
"<email-experts-keep-messages-on-server>`."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:16
msgid ""
"Zammad will **send an auto-reply message to every email it imports** "
"(including the old ones!). Use the *Experts* dialog to :ref:`change this "
"behavior <email-experts-import-as>` or to :doc:`disable auto-replies </"
"manage/trigger>` prior adding an email account and to turn it back on once "
"all your messages have been imported."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:26
msgid "**Gmail / G Suite users:**"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:25
msgid ""
"To add a Google account, create a dedicated :doc:`Google channel </channels/"
"google/basic-setup>`."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:30
msgid "**Microsoft 365 users:**"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:29
msgid ""
"To add a Microsoft 365 account, create a dedicated :doc:`Microsoft 365 IMAP "
"Email channel </channels/microsoft365/accounts>` or :doc:`Microsoft 365 "
"Graph Email channel </channels/microsoft365-graph/accounts>`."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:34
msgid "Basic"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:36
msgid ""
"In most cases, Zammad is smart enough to figure out your email provider's "
"configuration based on your email address alone. If the correct "
"configuration could not be retrieved, Zammad asks you to provide the correct "
"parameters manually."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:46
msgid "Screenshot showing basic email account setup inbound"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:46
msgid "Basic email account setup inbound"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:63
msgid "Organization & Department Name"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:49
#: ../channels/email/accounts/secondary-addresses.rst:26
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:56
#: ../channels/email/accounts/secondary-addresses.rst:33
msgid "A customer's inbox with an auto-reply from **Chrispresso Sales**."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:58
msgid ""
"If you add :doc:`multiple addresses <secondary-addresses>` to a single "
"account, you can define a separate Organization & Department Name for each "
"one."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:62
#: ../channels/email/accounts/secondary-addresses.rst:35
msgid ""
"Email display names value can be :ref:`further customized in the Settings "
"tab <email-settings-sender-format>`."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:73
#: ../channels/email/accounts/secondary-addresses.rst:39
#: ../channels/email/index.rst:2 ../channels/form.rst:20
#: ../system/objects/types.rst:154
msgid "Email"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:66
msgid "Your email address."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:68
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:71
msgid ""
"If your inbox receives mail for more than one email address, be sure to :doc:"
"`add your alternate addresses <secondary-addresses>` after account setup."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:76
#: ../channels/email/accounts/account-setup.rst:136
#: ../channels/email/accounts/account-setup.rst:238
#: ../channels/email/accounts/email-notification.rst:33
#: ../settings/security/password.rst:2
msgid "Password"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:76
#: ../channels/email/accounts/account-setup.rst:136
#: ../channels/email/accounts/account-setup.rst:236
#: ../channels/email/accounts/email-notification.rst:33
msgid "Your account password."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:83
#: ../channels/google/basic-setup.rst:154
#: ../channels/microsoft365/accounts/account-setup.rst:96
msgid "Destination group"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:79
#: ../channels/google/basic-setup.rst:150
#: ../channels/microsoft365/accounts/account-setup.rst:92
msgid ""
"The :doc:`group </manage/groups/index>` that incoming emails will be "
"assigned to."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:82
msgid ""
"Use :doc:`filters </channels/email/filters>` for more fine-grained sorting "
"of incoming email."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:94
#: ../channels/google/basic-setup.rst:165
#: ../channels/microsoft365/accounts/account-setup.rst:107
msgid "Destination group > Sending email address"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:86
#: ../channels/google/basic-setup.rst:157
#: ../channels/microsoft365/accounts/account-setup.rst:99
msgid ""
"Decide if the email address should be assigned to the selected group for "
"outgoing emails."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:89
msgid ""
"**Change to channel email address** will add this email address to the group "
"for outgoing emails. This may overwrite an already assigned email address."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:92
#: ../channels/microsoft365/accounts/account-setup.rst:105
msgid ""
"**Do not change email address** doesn't assign an email address to the group "
"or change it. If the group has no assigned email address, it stays empty. If "
"the group already has an assigned email address, it will stay the same."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:99
msgid "Experts"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:101
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:111
msgid ""
"When auto-detection fails, you will be presented with the \"Experts\"\n"
"account setup dialog."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:111
msgid "Expert configuration dialog"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:114
msgid "Email Inbound"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:122
#: ../misc/object-conditions/basics.rst:207 ../system/objects.rst:154
#: ../system/objects/types.rst:157
msgid "Type"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:117
msgid "Choose from **IMAP** and **POP3**."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:119
msgid ""
"In most cases, you want IMAP. (With POP3, you won't be able to :ref:`keep "
"messages on the server <email-experts-keep-messages-on-server>` or :ref:"
"`specify which folder to fetch from <email-experts-folder>`.)"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:127
#: ../channels/email/accounts/account-setup.rst:228
#: ../channels/email/accounts/email-notification.rst:24
msgid "Host"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:125
msgid ""
"Your email server's hostname or IP address (*e.g.,* ``imap.gmail.com``)."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:127
#: ../channels/email/accounts/account-setup.rst:158
msgid "Contact your email provider or system administrator if you don't know."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:133
#: ../channels/email/accounts/account-setup.rst:233
#: ../channels/email/accounts/email-notification.rst:30
#: ../misc/object-conditions/basics.rst:26
#: ../settings/security/third-party/microsoft.rst:68 ../system/sessions.rst:19
msgid "User"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:130
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:133
msgid "Adjust this setting in case your username and email address differ."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:145
msgid "SSL / STARTTLS"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:139
msgid "Enable encryption when fetching messages."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:141
msgid "You can choose from the following options:"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:143
msgid "No SSL (*not recommended!*)"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:144
msgid "SSL"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:145
msgid "STARTTLS"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:153
#: ../channels/email/accounts/account-setup.rst:252
#: ../manage/webhook/add.rst:72 ../settings/security/third-party/saml.rst:149
#: ../system/integrations/i-doit.rst:74
msgid "SSL verification"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:148
#: ../channels/email/accounts/account-setup.rst:246
msgid ""
"Here you can decide if the certificate of the email server has to be "
"verified or not (default: ``yes``). In case you are using custom "
"certificates, please have a look at :doc:`how to add them to Zammad </"
"settings/security/ssl-certificates>`."
msgstr ""

#: ../includes/ssl-verification-warning.rst:4
msgid ""
"Please be aware that **turning off SSL verification is a security risk**. It "
"should only be used temporarily or for testing purposes. If turned off, "
"there is no verification of the certificate, which means that any presented "
"certificate will be accepted."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:160
#: ../channels/email/accounts/account-setup.rst:243
#: ../channels/email/accounts/email-notification.rst:38
msgid "Port"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:156
msgid "Your email server's port (usu. ``993`` for IMAP, or ``995`` for POP3)."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:181
#: ../channels/google/basic-setup.rst:175
#: ../channels/microsoft365/accounts/account-setup.rst:118
msgid "Folder"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:163
msgid ""
"Specify which folder to fetch from, or leave empty to fetch from ``INBOX``."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:165
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:170
msgid ""
"If you selected a folder, additional steps may be required: 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:177
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:205
#: ../channels/google/basic-setup.rst:195
#: ../channels/microsoft365/accounts/account-setup.rst:140
msgid "Keep messages on server"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:184
#: ../channels/google/basic-setup.rst:178
#: ../channels/microsoft365/accounts/account-setup.rst:121
msgid "Specify what happens to your emails after Zammad imports them:"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:186
#: ../channels/google/basic-setup.rst:180
msgid "``no``: Zammad deletes all imported messages"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:188
#: ../channels/google/basic-setup.rst:181
msgid ""
"``yes``: Zammad marks imported messages as read. 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:193
#: ../channels/google/basic-setup.rst:185
#: ../channels/microsoft365/accounts/account-setup.rst:130
msgid "🤔 **Why does Zammad delete messages by default?**"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:195
#: ../channels/google/basic-setup.rst:187
#: ../channels/microsoft365/accounts/account-setup.rst:132
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:201
#: ../channels/google/basic-setup.rst:193
#: ../channels/microsoft365/accounts/account-setup.rst:138
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:209
#: ../channels/google/basic-setup.rst:198
#: ../channels/microsoft365/accounts/account-setup.rst:143
msgid "Archive Mode"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:0
#: ../channels/email/accounts/archive-mode.rst:7
#: ../channels/google/basic-setup.rst:0
#: ../channels/microsoft365/accounts/account-setup.rst:0
msgid "Archive Mode dialog during email account setup"
msgstr ""

#: ../channels/email/accounts/archive-mode.rst:7
msgid "How should old emails be imported?"
msgstr ""

#: ../channels/email/accounts/archive-mode.rst:9
msgid ""
"During the process of setting up an email based channel, Zammad checks if "
"emails are present in the inbox. If Zammad detects at least one email, the "
"archive mode dialog is triggered and the archive mode is turned on by "
"default. This dialog is also present if you edit an existing email based "
"channel. The archive mode lets you:"
msgstr ""

#: ../channels/email/accounts/archive-mode.rst:15
msgid ""
"Set an archive **cut-off time**, which means: older emails are imported in "
"archive mode, newer ones as standard tickets (including auto-reply messages "
"and in state \"new\")."
msgstr ""

#: ../channels/email/accounts/archive-mode.rst:18
msgid ""
"Select a **target state** for the archived emails: in most cases you might "
"want to import these archived emails in \"closed\" state. However, if your "
"use case is different, you can choose another one which fits for you."
msgstr ""

#: ../channels/email/accounts/archive-mode.rst:22
msgid ""
"By archiving emails, their creation date and time is preserved and no "
"automatic actions (e.g. trigger with auto-reply) will take place. If "
"imported as regular tickets, the date and time is always the time of the "
"import."
msgstr ""

#: ../channels/email/accounts/archive-mode.rst:26
msgid ""
"To import all emails as regular tickets, just turn the archive mode toggle "
"off."
msgstr ""

#: ../channels/email/accounts/archive-mode.rst:29
msgid ""
"If you turn off the archive mode, Zammad treats **all emails** (even old "
"ones) as if they had been sent today. This means senders will receive auto-"
"replies and tickets are created with state \"new\" for each message."
msgstr ""

#: ../channels/email/accounts/archive-mode.rst:33
msgid ""
"If you want to differentiate even more, you have to do it manually and "
"disable things like :doc:`triggers </manage/trigger>` before adding an email "
"account, depending on your use case."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:212
msgid "Email Outbound"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:219
msgid "Screenshot showing email setup outbound"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:219
msgid "Configuration dialog of email channel outbound"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:225
#: ../channels/email/accounts/email-notification.rst:21
msgid "Send mails via"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:222
#: ../channels/email/accounts/email-notification.rst:21
msgid "Choose from **SMTP** and **local MTA** (*e.g.,* Sendmail)."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:224
msgid ""
"Local MTA (mail transfer agent) configuration is only available on self-"
"hosted installations."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:228
#: ../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:231
#: ../channels/email/accounts/email-notification.rst:27
msgid "Your account login/username."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:233
#: ../channels/email/accounts/account-setup.rst:238
msgid "Leave blank to use the same value from incoming account setup."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:241
#: ../channels/email/accounts/email-notification.rst:36
msgid "Your email server's port (usu. ``587`` or ``465``)."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:243
#: ../channels/email/accounts/email-notification.rst:38
msgid "Zammad will detect and enable SSL/STARTTLS support automatically."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:255
msgid "Verification"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:None
msgid "Email account verification step"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:261
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:265
msgid ""
"We've created a `landing page for discard.zammad.org <https://discard.zammad."
"org>`_ which describes the backgrounds as well."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:270
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 ""
"If you did not assign the email address to the group, make sure to check if "
"the correct email address is :doc:`assigned to the group </manage/groups/"
"settings>`."
msgstr ""

#: ../channels/email/accounts/account-setup-group-hint.include.rst:5
msgid "Otherwise, the agents in this group will not be able to send e-mails."
msgstr ""

#: ../channels/email/accounts/account-setup.rst:276
#: ../channels/google/basic-setup.rst:256
#: ../channels/microsoft365/accounts/account-setup.rst:162
#: ../settings/security/third-party/saml.rst:186
#: ../system/integrations/cti/includes/troubleshooting.include.rst:2
#: ../system/integrations/github.rst:53 ../system/integrations/gitlab.rst:46
#: ../system/integrations/pgp/index.rst:112
#: ../system/integrations/smime/troubleshooting.rst:2
msgid "Troubleshooting"
msgstr ""

#: ../channels/email/accounts/account-setup.rst:278
msgid ""
":ref:`Is a custom incoming mail folder to blame? <email-experts-folder>`"
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:12
#: ../channels/email/accounts/managing-accounts.inbound-outbound.rst:11
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 <email-new-account-experts>` 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.rst:27
msgid "Destination Group"
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/basic-setup.rst:None
#: ../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/basic-setup.rst:208
msgid ""
"Only **active** groups will be displayed. Changing this setting will not "
"reassign existing tickets to the new group."
msgstr ""

#: ../channels/email/accounts/managing-accounts.rst:24
msgid ""
"You can assign the related outgoing email address to the new group by "
"choosing the option under **Destination group email address** or leave it as "
"it is. To assign an outgoing email address to a group manually, have a look "
"at the :doc:`group settings </manage/groups/settings>`."
msgstr ""

#: ../channels/email/accounts/managing-accounts.rst:38
msgid "Email Address"
msgstr ""

#: ../channels/email/accounts/managing-accounts.rst:30
msgid ""
"Use the **+ Add** or **Edit** buttons to set up secondary addresses on this "
"account."
msgstr ""

#: ../channels/email/accounts/managing-accounts.rst:33
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:46
msgid "Enabled / Disabled"
msgstr ""

#: ../channels/email/accounts/managing-accounts.rst:41
msgid ""
"Disabling an account temporarily prevents Zammad from importing its messages."
msgstr ""

#: ../channels/email/accounts/managing-accounts.rst:43
msgid ""
"This may be necessary during scheduled maintenance or when migrating your "
"installation to a new host."
msgstr ""

#: ../channels/email/accounts/managing-accounts.rst:46
msgid "Disabling an account disables *outgoing* messages for it, as well."
msgstr ""

#: ../channels/email/accounts/managing-accounts.rst:50
#: ../channels/email/accounts/managing-accounts.rst:51
#: ../manage/calendars.rst:29 ../manage/knowledge-base.rst:157
#: ../manage/knowledge-base.rst:189
msgid "Delete"
msgstr ""

#: ../channels/email/accounts/managing-accounts.rst:49
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 <secondary-"
"addresses>` **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
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 than the one from the account."
msgstr ""

#: ../channels/email/accounts/secondary-addresses.rst:7
msgid ""
"You can add an additional email address by clicking the ``+ Add`` button in "
"an existing account configuration. This opens a dialog where you can add "
"your address:"
msgstr ""

#: ../channels/email/accounts/secondary-addresses.rst:16
msgid "Screenshot shows adding a secondary address"
msgstr ""

#: ../channels/email/accounts/secondary-addresses.rst:16
msgid ""
"Add a secondary address and 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:21
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:36
msgid "Display Name"
msgstr ""

#: ../channels/email/accounts/secondary-addresses.rst:39
msgid "The alias address to send outgoing messages as."
msgstr ""

#: ../channels/email/accounts/secondary-addresses.rst:42
#: ../channels/microsoft365/accounts/account-setup.rst:84
msgid "Channel"
msgstr ""

#: ../channels/email/accounts/secondary-addresses.rst:42
msgid ""
"The email account to be used when sending outgoing messages from this alias."
msgstr ""

#: ../channels/email/accounts/secondary-addresses.rst:45
#: ../channels/email/accounts/secondary-addresses.rst:46
#: ../manage/groups/settings.rst:102 ../manage/macros/how-do-they-work.rst:0
#: ../manage/macros/learn-by-example.rst:0
#: ../manage/roles/admin-permissions.rst:40
#: ../manage/roles/agent-permissions.rst:31
#: ../manage/roles/user-preferences-permissions.rst:37
#: ../manage/scheduler.rst:108 ../manage/webhook/add.rst:116
#: ../misc/variables.rst:101
#: ../system/integrations/cti/includes/inbound-calls.include.rst:15
#: ../system/integrations/cti/includes/outbound-calls.include.rst:18
#: ../system/integrations/cti/includes/inbound-calls.include.rst:14
#: ../system/integrations/cti/includes/outbound-calls.include.rst:17
#: ../system/objects.rst:162 ../system/objects.rst:246
msgid "Note"
msgstr ""

#: ../channels/email/accounts/secondary-addresses.rst:45
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 :"
"docs:`Administration via Console </admin/console.html>`."
msgstr ""

#: ../channels/email/advanced/fetchmail.rst:14
msgid "**Command line**::"
msgstr ""

#: ../channels/email/advanced/fetchmail.rst:22
msgid "Fetchmail"
msgstr ""

#: ../channels/email/advanced/fetchmail.rst:24
msgid "**Create .fetchmailrc**::"
msgstr ""

#: ../channels/email/advanced/fetchmail.rst:32
#: ../channels/email/advanced/fetchmail.rst:52
msgid "**vi .fetchmailrc**::"
msgstr ""

#: ../channels/email/advanced/fetchmail.rst:40
msgid "That's it. Emails now will be directly piped into Zammad."
msgstr ""

#: ../channels/email/advanced/fetchmail.rst:45
msgid "Using Procmail for Advanced Features Like Presorting"
msgstr ""

#: ../channels/email/advanced/fetchmail.rst:47
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:50
msgid "Fetchmail config looks slightly different."
msgstr ""

#: ../channels/email/advanced/fetchmail.rst:60
msgid "**Create .procmailrc**::"
msgstr ""

#: ../channels/email/advanced/fetchmail.rst:66
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 "Header Based Actions"
msgstr ""

#: ../channels/email/email-headers.rst:5
msgid ""
"With specific email headers, you can make Zammad perform different actions "
"depending on the content of the headers. So, if you create a new email (e.g. "
"from a form on your website) you can set these headers to perform actions or "
"to hand over special information like custom attributes."
msgstr ""

#: ../channels/email/email-headers.rst:10
msgid "**🛡 Trusted channels required 🛡**"
msgstr ""

#: ../channels/email/email-headers.rst:12
msgid ""
"This feature is a potential risk with external communication and thus "
"require channels being set to trusted explicitly. You can find instructions "
"about how to set a channel to trusted at the end of this page."
msgstr ""

#: ../channels/email/email-headers.rst:18
msgid ""
"The header names listed below are examples and in our opinion the most "
"relevant ones. However, you can adjust mostly all article or ticket "
"attributes including custom ones if you know the attribute's exact name. "
"Have a look :doc:`here </system/objects>` to find the attribute names."
msgstr ""

#: ../channels/email/email-headers.rst:22
msgid ""
"Please note that while header names are case insensitive, header values are "
"not. Make sure to specify values in expected case, otherwise they will not "
"match."
msgstr ""

#: ../channels/email/email-headers.rst:27
msgid "Auto Responses"
msgstr ""

#: ../channels/email/email-headers.rst:29
msgid ""
"Normally, Zammad runs internal checks to see if an incoming email is an "
"automatic response. In such cases Zammad will not send trigger based "
"responses. You can override this with the below mentioned headers:"
msgstr ""

#: ../channels/email/email-headers.rst:38
msgid "``x-zammad-send-auto-response``"
msgstr ""

#: ../channels/email/email-headers.rst:34
msgid ""
"Set to ``false`` to disable trigger based responses. If set to ``true`` "
"Zammad will send a response."
msgstr ""

#: ../channels/email/email-headers.rst:37
msgid ""
"This option *does not* work if e.g. ``precedence: list`` is set unless you "
"use the auto response header below as well."
msgstr ""

#: ../channels/email/email-headers.rst:48
msgid "``x-zammad-is-auto-response``"
msgstr ""

#: ../channels/email/email-headers.rst:41
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:45
msgid "Set this header to ``false`` if you want to generate auto responses."
msgstr ""

#: ../channels/email/email-headers.rst:47
msgid ""
"This header allows you to overwrite auto detects for e.g. ``precedence: "
"list``."
msgstr ""

#: ../channels/email/email-headers.rst:51
#: ../system/integrations/checkmk/api-reference.rst:113
msgid "Ticket Attributes"
msgstr ""

#: ../channels/email/email-headers.rst:53
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 override headers."
msgstr ""

#: ../channels/email/email-headers.rst:57
msgid "To differentiate between ticket creation and follow-up:"
msgstr ""

#: ../channels/email/email-headers.rst:59
msgid "For creations use: ``X-Zammad-Ticket-{Attribute Name}``"
msgstr ""

#: ../channels/email/email-headers.rst:60
msgid "For follow ups use: ``X-Zammad-Ticket-FollowUp-{Attribute Name}``"
msgstr ""

#: ../channels/email/email-headers.rst:62
msgid ""
"This allows you to ensure the changes are only applied in the required "
"situation."
msgstr ""

#: ../channels/email/email-headers.rst:67
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, you can use one of "
"the following examples:"
msgstr ""

#: ../channels/email/email-headers.rst:71
msgid "``2021-09-28T08:00:00+0200``"
msgstr ""

#: ../channels/email/email-headers.rst:72
msgid "``2021-09-28T08:00:00+02:00``"
msgstr ""

#: ../channels/email/email-headers.rst:73
msgid "``2021-09-28T06:00:00.000Z``"
msgstr ""

#: ../channels/email/email-headers.rst:77
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:81
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:86
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:94
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 "Example: ``X-Zammad-Ticket-Pending_Time: 2021-09-26T08:00:00+0200``"
msgstr ""

#: ../channels/email/email-headers.rst:101
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:101
#: ../channels/email/email-headers.rst:108
msgid "This header is not available for follow ups."
msgstr ""

#: ../channels/email/email-headers.rst:108
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:111
msgid "Article Attributes"
msgstr ""

#: ../channels/email/email-headers.rst:113
msgid ""
"If needed Zammad allows you to manipulate attributes or states of fetched "
"email articles."
msgstr ""

#: ../channels/email/email-headers.rst:125
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:120
msgid ""
"System Emails are indicated in a similar way as trigger-responses. Users "
"can't see them natively and see only a indicator like that:"
msgstr ""

#: ../channels/email/email-headers.rst:0
msgid "Received mail as article sender system"
msgstr ""

#: ../channels/email/email-headers.rst:135
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:134
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:139
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:143
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/email-headers.rst:146
msgid "Trusted Channel"
msgstr ""

#: ../channels/email/email-headers.rst:147
#: ../settings/system/system-selfhosted.include.rst:1
msgid "**🚧 Self Hosted only 🚧**"
msgstr ""

#: ../channels/email/email-headers.rst:149
msgid "The settings below are only available to self hosted users."
msgstr ""

#: ../channels/email/email-headers.rst:152
msgid ""
"⚠️ As stated above, this is dangerous and can lead to unexpected behavior in "
"the communication with external parties. Only follow the instructions below "
"if you know what you are doing."
msgstr ""

#: ../channels/email/email-headers.rst:156
msgid ""
"Setting a channel to ``trusted`` can ony be done via :docs:`console </admin/"
"console.html>`. In the rails console, execute the following commands:"
msgstr ""

#: ../channels/email/email-headers.rst:160
msgid "List all channels in Zammad:"
msgstr ""

#: ../channels/email/email-headers.rst:166
msgid "Look for the ``id`` of the channel, you want to set to ``trusted``."
msgstr ""

#: ../channels/email/email-headers.rst:168
msgid "Select your identified channel (replace the 99 with the correct id):"
msgstr ""

#: ../channels/email/email-headers.rst:174
msgid "Show the currently activated options of the selected channel:"
msgstr ""

#: ../channels/email/email-headers.rst:180
msgid "Add the ``\"trusted\"=>true`` flag for the inbound part of the channel:"
msgstr ""

#: ../channels/email/email-headers.rst:186
msgid "Save your changes:"
msgstr ""

#: ../channels/email/filters.rst:2
msgid "Filters"
msgstr ""

#: ../channels/email/filters.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 ""
"Different attributes of a filter can be combined with each other. Likewise, "
"the following operators can be combined. The supported matches are:"
msgstr ""

#: ../channels/email/filters.rst:25
msgid "*contains*"
msgstr ""

#: ../channels/email/filters.rst:26
msgid "*contains not*"
msgstr ""

#: ../channels/email/filters.rst:27
msgid "*is any of*"
msgstr ""

#: ../channels/email/filters.rst:28
msgid "*is none of*"
msgstr ""

#: ../channels/email/filters.rst:29
msgid "*starts with one of*"
msgstr ""

#: ../channels/email/filters.rst:30
msgid "*ends with one of*"
msgstr ""

#: ../channels/email/filters.rst:31
msgid "*matches regex*"
msgstr ""

#: ../channels/email/filters.rst:32
msgid "*does not match regex*"
msgstr ""

#: ../channels/email/filters.rst:34
msgid ""
"You can also have a look at the :doc:`object conditions </misc/object-"
"conditions/basics>` for text fields, where you can find a description of how "
"the operators are working."
msgstr ""

#: ../channels/email/filters.rst:40
msgid ""
"Please note that the ticket actions are separated in \"Ticket creation\" and "
"\"Ticket update\". Make sure to use the appropriate variant for your "
"scenario."
msgstr ""

#: ../channels/email/filters.rst:43
msgid "Here are some examples of what is possible with filters:"
msgstr ""

#: ../channels/email/filters.rst:50
msgid "Automatically dispatch tickets into certain groups:"
msgstr ""

#: ../channels/email/filters.rst:46
msgid ""
"For example, tickets from ``amazon.com`` could automatically be dispatched "
"to the Purchasing group."
msgstr ""

#: ../channels/email/filters.rst:0
msgid "From: *matches regex:* ``(\\.|@)amazon\\.com``"
msgstr ""

#: ../channels/email/filters.rst:0
msgid "Group: Purchasing"
msgstr ""

#: ../channels/email/filters.rst:54
msgid ""
"Automatically dispatch tickets to responsible staff based on organization "
"name:"
msgstr ""

#: ../channels/email/filters.rst:0
msgid "Organization: *starts with one of:* ``A`` ``B`` ``C``"
msgstr ""

#: ../channels/email/filters.rst:0
msgid "Owner: Emily Adams"
msgstr ""

#: ../channels/email/filters.rst:58
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:63
msgid ""
"Automatically tag and close spam tickets that have been marked as spam by an "
"external 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:65
msgid ""
"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 <https://community.zammad.org>`_."
msgstr ""

#: ../channels/email/filters/system-filters.rst:14
msgid "Service-Now"
msgstr ""

#: ../channels/email/filters/system-filters.rst:16
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:19
msgid "Headers contain the ``X-ServiceNow-Generated`` header."
msgstr ""

#: ../channels/email/filters/system-filters.rst:20
msgid "Subject does match the regex ``\\s(INC\\d+)\\s`` e.g. ``INC678439``."
msgstr ""

#: ../channels/email/filters/system-filters.rst:22
msgid ""
"See `Service-Now Mail Example <https://github.com/zammad/zammad/blob/stable/"
"test/data/mail/mail090.box>`_ for comparison of your emails."
msgstr ""

#: ../channels/email/filters/system-filters.rst:26
msgid "JIRA"
msgstr ""

#: ../channels/email/filters/system-filters.rst:28
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:31
msgid "Headers contain the ``X-JIRA-FingerPrint`` header."
msgstr ""

#: ../channels/email/filters/system-filters.rst:32
msgid ""
"Subject does match the regex ``\\[JIRA\\]\\s\\((\\w+-\\d+)\\)`` e.g. "
"``[JIRA] (SYS-422)``."
msgstr ""

#: ../channels/email/filters/system-filters.rst:35
msgid ""
"See `JIRA Mail Example <https://github.com/zammad/zammad/blob/stable/test/"
"data/mail/mail103.box>`_ 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 </channels/google/index>` instead."
msgstr ""

#: ../channels/email/index.rst:22
msgid "**Using Microsoft 365?**"
msgstr ""

#: ../channels/email/index.rst:21
msgid ""
"Set up a :doc:`Microsoft 365 IMAP </channels/microsoft365/index>` or :doc:"
"`Microsoft 365 Graph channel </channels/microsoft365-graph/index>` instead."
msgstr ""

#: ../channels/email/index.rst:None
#: ../channels/microsoft365-graph/index.rst:None
#: ../channels/microsoft365/index.rst:None
msgid "Email settings panel"
msgstr ""

#: ../channels/email/index.rst:41
msgid "🚛 Migrate existing email channel to \"XOAUTH\" channel"
msgstr ""

#: ../channels/email/index.rst:30
msgid "At this moment Zammad supports XOAUTH for the following providers:"
msgstr ""

#: ../channels/email/index.rst:32
msgid ":ref:`Google Email <migrate-channel>`"
msgstr ""

#: ../channels/email/index.rst:33
msgid ""
":doc:`Microsoft 365 IMAP Email </channels/microsoft365/accounts/migrate-from-"
"email-channel>` (formerly Office 365)"
msgstr ""

#: ../channels/email/index.rst:37
msgid ""
"Microsoft 365 *Graph* Email supports XOAUTH as well, but currently there is "
"no migration option. Instead, you have to remove the existing and :doc:`add "
"the new channel manually </channels/microsoft365-graph/accounts/>`."
msgstr ""

#: ../channels/email/index.rst:50 ../channels/email/index.rst:10
msgid ":doc:`👥 Accounts <accounts>`"
msgstr ""

#: ../channels/email/index.rst:44 ../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:47 ../channels/email/index.rst:7
msgid ""
"(Self-hosted users may have already completed this step during new system "
"setup.)"
msgstr ""

#: ../channels/email/index.rst:54 ../channels/email/index.rst:14
msgid ":doc:`🗂️ Filters <filters>`"
msgstr ""

#: ../channels/email/index.rst:53 ../channels/email/index.rst:13
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:57 ../channels/email/index.rst:17
msgid ":doc:`📜  Signatures <signatures>`"
msgstr ""

#: ../channels/email/index.rst:57 ../channels/email/index.rst:17
msgid "Customize signatures for all outgoing email."
msgstr ""

#: ../channels/email/index.rst:69 ../channels/email/index.rst:29
msgid ":doc:`⚙️  Settings <settings>`"
msgstr ""

#: ../channels/email/index.rst:60 ../channels/google/index.rst:42
#: ../channels/email/index.rst:20
msgid "Manage options like:"
msgstr ""

#: ../channels/email/index.rst:62 ../channels/google/index.rst:44
#: ../channels/email/index.rst:22
msgid "set the “From:” address on system notifications"
msgstr ""

#: ../channels/email/index.rst:63 ../channels/google/index.rst:45
#: ../channels/email/index.rst:23
msgid "raise the limit on attachment sizes"
msgstr ""

#: ../channels/email/index.rst:64 ../channels/google/index.rst:46
#: ../channels/email/index.rst:24
msgid "modify subject-line prefixes (*e.g.,* use “AW:” instead of “RE:”)"
msgstr ""

#: ../channels/email/index.rst:66 ../channels/email/index.rst:26
msgid ""
"Want to **manually edit email subjects** or **always copy parent messages "
"into your replies**?"
msgstr ""

#: ../channels/email/index.rst:69 ../channels/email/index.rst:29
msgid "Check the ✍️ :doc:`/misc/composer`."
msgstr ""

#: ../channels/email/index.rst:74 ../channels/email/index.rst:35
msgid ":doc:`📇 Header based actions <email-headers>`"
msgstr ""

#: ../channels/email/index.rst:72 ../channels/google/index.rst:49
#: ../channels/email/index.rst:32
msgid "Manipulate auto response behavior or incoming routing."
msgstr ""

#: ../channels/email/index.rst:74 ../channels/google/index.rst:51
#: ../channels/email/index.rst:34
msgid "🤓 This is a very advanced topic."
msgstr ""

#: ../channels/email/index.rst:77
msgid "Extra Options for Self-Hosted Users"
msgstr ""

#: ../channels/email/index.rst:79
msgid "If you're too cool for POP3/IMAP/SMTP..."
msgstr ""

#: ../channels/email/settings.rst:2 ../channels/form.rst:28 ../index.rst:57
#: ../manage/time-accounting.rst:15
#: ../system/integrations/checkmk/admin-panel-reference.rst:5
msgid "Settings"
msgstr ""

#: ../channels/email/settings.rst:None
msgid "Settings section in email channel"
msgstr ""

#: ../channels/email/settings.rst:7
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:10
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:14
msgid "List of Settings"
msgstr ""

#: ../channels/email/settings.rst:23
msgid ""
"Notification Sender: Default value ``Notification Master <noreply@#{config."
"fqdn}>``"
msgstr ""

#: ../channels/email/settings.rst:17
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:22
msgid ""
"This address is relevant for agent notifications and password reset mails "
"(also affects customers)."
msgstr ""

#: ../channels/email/settings.rst:53
msgid "Additional follow-up detection: Default value ``Subject & References``"
msgstr ""

#: ../channels/email/settings.rst:26
msgid ""
"Adjust how Zammad checks if an incoming email is a follow-up or not. If you "
"disable all checks, Zammad only checks if a matching ticket hook & number is "
"present in the subject."
msgstr ""

#: ../channels/email/settings.rst:33
msgid "Subject & References"
msgstr ""

#: ../channels/email/settings.rst:31
msgid ""
"Checks subject and message IDs of emails and searches for initial ticket "
"articles with the same subject and message ID. When both are matching, it is "
"considered as a follow-up."
msgstr ""

#: ../channels/email/settings.rst:37
msgid "References"
msgstr ""

#: ../channels/email/settings.rst:36
msgid ""
"Additionally checks if a message ID from email matches an existing article."
msgstr ""

#: ../channels/email/settings.rst:42
msgid "Attachment"
msgstr ""

#: ../channels/email/settings.rst:40
msgid ""
"Additionally checks attachments of emails. Useful if you often get emails "
"forwarded as attachments and want to have them in existing tickets, if there "
"is a reference included in an attached email."
msgstr ""

#: ../channels/email/settings.rst:49
msgid "Body"
msgstr ""

#: ../channels/email/settings.rst:45
msgid ""
"Additionally checks the body of emails. If there is a ticket identifier "
"(ticket hook & number) in the body, it is considered as a follow-up. Useful "
"if you want to add emails to existing tickets which are completely "
"independent but talking about existing tickets including such a ticket "
"reference."
msgstr ""

#: ../channels/email/settings.rst:51
msgid ""
"Please note that activating additional checks can lead to false detection. "
"In production environments, you should change this setting very carefully "
"and monitor the behavior afterwards."
msgstr ""

#: ../channels/email/settings.rst:58
msgid "Maximum Email Size: Default value ``10 MB``"
msgstr ""

#: ../channels/email/settings.rst:56
msgid ""
"This one is pretty obvious: It defines the maximum allowed size of an email "
"Zammad will fetch. Zammad will not fetch emails that are bigger than this "
"option (*including attachments!*)."
msgstr ""

#: ../channels/email/settings.rst:76
msgid "Send postmaster mail if mail too large: Default value ``yes (enabled)``"
msgstr ""

#: ../channels/email/settings.rst:68 ../channels/email/settings.rst:97
msgid "Option set to ``yes``"
msgstr ""

#: ../channels/email/settings.rst:62
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:67
msgid ""
"Nevertheless, Zammad will remove the mail from the mailbox (if enabled)."
msgstr ""

#: ../channels/email/settings.rst:76 ../channels/email/settings.rst:100
msgid "Option set to ``no``"
msgstr ""

#: ../channels/email/settings.rst:71
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:76
msgid "Learn more about :doc:`/system/monitoring`."
msgstr ""

#: ../channels/email/settings.rst:90
msgid "Sender based on Reply-To header: Default value ``not set (-)``"
msgstr ""

#: ../channels/email/settings.rst:79
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:85
msgid "Option set to ``Take reply-to header as sender/from of email.``"
msgstr ""

#: ../channels/email/settings.rst:84
msgid ""
"This setting will overwrite the initial ``FROM`` to the value used in "
"``Reply-To`` completely."
msgstr ""

#: ../channels/email/settings.rst:90
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:88
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:106
msgid ""
"Customer selection based on sender and receiver list: Default value ``yes``"
msgstr ""

#: ../channels/email/settings.rst:93
msgid ""
"This option decides how Zammad should react if an agent sends a email to it."
msgstr ""

#: ../channels/email/settings.rst:96
msgid ""
"The first user / email address from the recipient list will be used as the "
"ticket customer."
msgstr ""

#: ../channels/email/settings.rst:100
msgid "The agent will be set as ticket customer."
msgstr ""

#: ../channels/email/settings.rst:104
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:116
msgid "Block Notifications"
msgstr ""

#: ../channels/email/settings.rst:109
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:113
msgid ""
"The default value is: ``(mailer-daemon|postmaster|abuse|root|noreply|noreply."
"+?|no-reply|no-reply.+?)@.+?``"
msgstr ""

#: ../channels/email/settings.rst:143
msgid ""
"Sender Format: Default value ``Agent Name + FromSeparator + System Address "
"Display Name``"
msgstr ""

#: ../channels/email/settings.rst:119
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:143
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:142
msgid ""
"If you want to remove the ticket reference from the subject, you can learn "
"more in :doc:`Settings > Ticket </settings/ticket>`."
msgstr ""

#: ../channels/email/settings.rst:147
msgid "Sender Format Separator: Default value ``via``"
msgstr ""

#: ../channels/email/settings.rst:146
msgid ""
"This 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:153
msgid "Ticket Subject Forward: Default value ``FWD``"
msgstr ""

#: ../channels/email/settings.rst:150
msgid ""
"The above string will be used on the subject if you forward an email from "
"Zammad."
msgstr ""

#: ../channels/email/settings.rst:153 ../channels/email/settings.rst:159
msgid "``:`` will be automatically appended to the above string."
msgstr ""

#: ../channels/email/settings.rst:159
msgid "Ticket Subject Reply: Default value ``RE``"
msgstr ""

#: ../channels/email/settings.rst:156
msgid ""
"The above string will be used on the subject if you reply to a mail from "
"Zammad."
msgstr ""

#: ../channels/email/settings.rst:171
msgid "Ticket Subject Size: Default value ``110``"
msgstr ""

#: ../channels/email/settings.rst:162
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:167
msgid ""
"This does *not* limit ticket titles within the UI, just the subjects when "
"replying to an email."
msgstr ""

#: ../channels/email/settings.rst:170
msgid "Example: ``RE: Test somew[...] [Ticket#123456]``"
msgstr ""

#: ../channels/email/settings.rst:174
msgid "Enhanced Settings"
msgstr ""

#: ../channels/email/settings.rst:176
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 :"
"docs:`within the advanced customization settings </admin/console/hidden-"
"settings.html>`."
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:20
msgid "Dynamic Signatures"
msgstr ""

#: ../channels/email/signatures.rst:22
msgid ""
"To individualize the signatures, it is possible to automatically load "
"specific information into a signature via :doc:`/misc/variables`. All "
"information stored on the ticket, assigned customers or agents can be "
"inserted. This makes it possible to design the signature individually. To "
"load a list of available variables, enter two colons (``::``) into the "
"*Text* box of the signature editor."
msgstr ""

#: ../channels/email/signatures.rst:31
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:39
msgid ""
"Here is an example of a signature with variables and the result when you "
"write a mail:"
msgstr ""

#: ../channels/facebook.rst:2 ../misc/first-steps.rst:84
#: ../settings/security/third-party/facebook.rst:2
msgid "Facebook"
msgstr ""

#: ../channels/facebook.rst:7
msgid ""
"You can connect your Facebook account to Zammad, allowing you to create "
"tickets from posts and respond as comments."
msgstr ""

#: ../channels/facebook.rst:10
msgid ""
"Please note that you first and foremost should have a look at `Meta's "
"documentation <https://developers.facebook.com/docs/>`_ to get the most "
"recent and substantial information for the steps on their side. Some steps "
"on Meta's side are only mentioned here as prerequisites, as this is outside "
"the scope of this documentation."
msgstr ""

#: ../channels/facebook.rst:16
msgid ""
"The setup of the :doc:`WhatsApp channel </channels/whatsapp/index>` has "
"similar prerequisites as the Facebook channel. So, if you managed to set one "
"of them to up, you should have a look at the other one too. It could be a "
"low hanging fruit! 🎉"
msgstr ""

#: ../channels/facebook.rst:22 ../channels/whatsapp/prerequisites.rst:2
#: ../settings/security/ssl-certificates.rst:17
#: ../system/integrations/smime/prerequisites.rst:2
msgid "Prerequisites"
msgstr ""

#: ../channels/facebook.rst:24
msgid "`Meta business account <https://business.facebook.com/overview>`_"
msgstr ""

#: ../channels/facebook.rst:25
msgid ""
"`Meta developer account <https://developers.facebook.com/docs/development/"
"register>`_"
msgstr ""

#: ../channels/facebook.rst:26
msgid ""
"Permission to create an app inside your developer account and needed "
"information for the app (see `here <https://developers.facebook.com/docs/"
"development/create-an-app>`_)"
msgstr ""

#: ../channels/facebook.rst:30
msgid "Creating an App"
msgstr ""

#: ../channels/facebook.rst:53
msgid "Create a new app"
msgstr ""

#: ../channels/facebook.rst:33
msgid ""
"Go to Meta's `app dashboard <https://developers.facebook.com/apps>`_ and "
"create a new app."
msgstr ""

#: ../channels/facebook.rst:0
msgid ""
"Screenshot of Meta's app dashboard with highlighted \"Create App\" button"
msgstr ""

#: ../channels/facebook.rst:39
msgid "If you have more than one business portfolio, select the desired one."
msgstr ""

#: ../channels/facebook.rst:41
msgid "In the \"Use cases\" tab, select \"Other\" and \"Business\" app type."
msgstr ""

#: ../channels/facebook.rst:0
msgid "Screenshot of app creation with highlighted app type"
msgstr ""

#: ../channels/facebook.rst:49
msgid ""
"In the next screen, provide a fitting app name, contact email address and "
"select your business portfolio and finally click on \"Create app\"."
msgstr ""

#: ../channels/facebook.rst:0
msgid "Screenshot of app creation on \"Details\" tab"
msgstr ""

#: ../channels/facebook.rst:72 ../channels/whatsapp/preparation.rst:None
msgid "Add a product to your app"
msgstr ""

#: ../channels/facebook.rst:56
msgid ""
"After creating the app, you should see the app overview, where you can add a "
"product to your app."
msgstr ""

#: ../channels/facebook.rst:59
msgid ""
"Scroll down and select \"Facebook Login for Business\" by clicking on the "
"\"Set up\" button."
msgstr ""

#: ../channels/facebook.rst:0
msgid ""
"Screenshot of product overview with highlighted \"Facebook Login for "
"Business\""
msgstr ""

#: ../channels/facebook.rst:65
msgid ""
"In the following screen, go to \"Valid OAuth Redirect URIs\" and provide the "
"URL of your Zammad instance, followed by ``/api/v1/external_credentials/"
"facebook/callback``. You can copy this URL from Zammad if you click on the "
"\"Configure App\" button in Zammad's Facebook channel admin screen."
msgstr ""

#: ../channels/facebook.rst:0
msgid "Screenshot of app settings with highlighted \"OAuth Redirect URIs\""
msgstr ""

#: ../channels/facebook.rst:74
msgid ""
"Continue with the next step on Zammad's side by connecting the Facebook with "
"Zammad."
msgstr ""

#: ../channels/facebook.rst:78
msgid "Connect Facebook App in Zammad"
msgstr ""

#: ../channels/facebook.rst:80
msgid ""
"If not already done, go to the Facebook channel section in the admin "
"interface in Zammad and click on \"Configure App\". This will open a dialog "
"where you have to provide the app ID as well as the app secret."
msgstr ""

#: ../channels/facebook.rst:84
msgid ""
"Head over to the Meta app dashboard and switch to \"App settings\" > "
"\"Basic\". Copy the \"App ID\" and the the \"App secret\" (after clicking on "
"the \"Show\" button) and paste both to Zammad in the corresponding fields."
msgstr ""

#: ../channels/facebook.rst:None
msgid "Screenshot showing basic settings section of app settings"
msgstr ""

#: ../channels/facebook.rst:None
msgid "Screenshot showing \"Connect Facebook App\" dialog in Zammad"
msgstr ""

#: ../channels/facebook.rst:96
msgid "Confirm it by clicking on \"Submit\" and continue with the next step."
msgstr ""

#: ../channels/facebook.rst:99
msgid "Add Facebook Account to Zammad"
msgstr ""

#: ../channels/facebook.rst:101
msgid ""
"After you successfully connected your app with Zammad, you can now add an "
"account by clicking the \"Add Account\" button in Zammad. This redirects you "
"to Facebook and you will see an account selection dialog. Confirm by "
"clicking on \"Continue as ...\" or log in with another account."
msgstr ""

#: ../channels/facebook.rst:None
msgid "Screenshot showing Account selection from Meta"
msgstr ""

#: ../channels/facebook.rst:111
msgid ""
"In the next screen you can choose if you want to receive tickets from all "
"pages or just selected ones. Choose what fits your needs and confirm by "
"clicking \"Continue\"."
msgstr ""

#: ../channels/facebook.rst:None
msgid "Screenshot showing pages selection from Meta"
msgstr ""

#: ../channels/facebook.rst:120
msgid ""
"Finally, you see an overview about the requested permission. Click on "
"\"Save\" and \"Got it\" in the next screen."
msgstr ""

#: ../channels/facebook.rst:None
msgid "Screenshot showing permission overview"
msgstr ""

#: ../channels/facebook.rst:128
msgid ""
"You are now redirected to Zammad where you can see a configuration dialog. "
"Select a group you want to handle the Facebook tickets and click on "
"\"Submit\"."
msgstr ""

#: ../channels/facebook.rst:None
msgid "Screenshot showing group selection dialog in Zammad"
msgstr ""

#: ../channels/facebook.rst:136
msgid ""
"After that, you are technically ready to go. However, you have to do some "
"additional steps, which aren't covered in this documentation:"
msgstr ""

#: ../channels/facebook.rst:139
msgid "Request advanced access for your app (see screenshot below)"
msgstr ""

#: ../channels/facebook.rst:140
msgid "Request a business review if your business is not already reviewed"
msgstr ""

#: ../channels/facebook.rst:141
msgid "Switch your app from development to live mode"
msgstr ""

#: ../channels/facebook.rst:None
msgid ""
"Screenshot showing permission and features screen in the Facebook developer "
"portal"
msgstr ""

#: ../channels/form.rst:2
msgid "Form"
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 ../channels/whatsapp/limitations.rst:2
#: ../manage/trigger/limitations.rst:2
#: ../settings/security/third-party/microsoft.rst:19
#: ../system/core-workflows/limitations.rst:2
#: ../system/integrations/cti/includes/introduction.include.rst:18
#: ../system/integrations/elasticsearch.rst:25
#: ../system/integrations/ldap/index.rst:28
#: ../system/integrations/smime/prerequisites.rst:83
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:16
#: ../manage/scheduler.rst:39 ../manage/slas/how-do-they-work.rst:26
#: ../manage/templates.rst:33 ../system/objects.rst:131
#: ../system/objects.rst:234
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:37 ../manage/groups/settings.rst:123
#: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0
#: ../manage/roles/index.rst:128 ../manage/scheduler.rst:111
#: ../manage/templates.rst:43 ../manage/webhook/add.rst:123
#: ../system/objects.rst:169 ../system/objects.rst:248
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:36
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:41
msgid "Group selection for ticket creation"
msgstr ""

#: ../channels/form.rst:40
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:44
msgid "Designer"
msgstr ""

#: ../channels/form.rst:46
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:52
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:61
msgid "So let's talk about the options the designer provides."
msgstr ""

#: ../channels/form.rst:68
msgid "Title of the form"
msgstr ""

#: ../channels/form.rst:64
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:68
msgid "Default: ``Feedback Form``"
msgstr ""

#: ../channels/form.rst:73
msgid "Name of form submit button"
msgstr ""

#: ../channels/form.rst:71
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:84
msgid "Message after sending form"
msgstr ""

#: ../channels/form.rst:76
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:79
msgid "Default *after* sending a form will look like so:"
msgstr ""

#: ../channels/form.rst:140
msgid "Options"
msgstr ""

#: ../channels/form.rst:87
msgid ""
"Zammad provides the following additional configuration options for your form."
msgstr ""

#: ../channels/form.rst:93
msgid "Enable debugging for implementation"
msgstr ""

#: ../channels/form.rst:90
msgid ""
"This option activates detailed debug information in your browser's developer "
"tools console."
msgstr ""

#: ../channels/form.rst:93
msgid "This option *should not* be active on productive forms!"
msgstr ""

#: ../channels/form.rst:97
msgid "Show title in form"
msgstr ""

#: ../channels/form.rst:96
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:107
msgid "Start modal dialog for form"
msgstr ""

#: ../channels/form.rst:100
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:104
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:107
msgid "This option is set by default."
msgstr ""

#: ../channels/form.rst:114
msgid ""
"Don't load CSS for the form You need to generate your own CSS for the form."
msgstr ""

#: ../channels/form.rst:110
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:113
msgid ""
"Selecting this option allows you to freely design the form without having to "
"overwrite existing directives."
msgstr ""

#: ../channels/form.rst:125
msgid "Add attachment option to upload"
msgstr ""

#: ../channels/form.rst:117
msgid "Allows your user to upload **one attachment** to the form."
msgstr ""

#: ../channels/form.rst:119
msgid ""
"The allowed attachment sizes *is not* limited. The only limitation that "
"applies is your web servers upload limit."
msgstr ""

#: ../channels/form.rst:122
msgid "**SaaS only**"
msgstr ""

#: ../channels/form.rst:124
msgid ""
"If you're with Zammad hosted, attachments are limited by the package you've "
"chosen."
msgstr ""

#: ../channels/form.rst:140
msgid "Add agreement text before submit"
msgstr ""

#: ../channels/form.rst:128
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:137
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:140
msgid "This allows you to link e.g. to your data privacy or ToS information."
msgstr ""

#: ../channels/form.rst:143 ../manage/scheduler.rst:62
#: ../manage/slas/how-do-they-work.rst:35 ../system/objects/types.rst:297
msgid "Preview"
msgstr ""

#: ../channels/form.rst:145
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:148
msgid ""
"Clicking on the button will open the form modal. 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:158
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:174
msgid "Header section"
msgstr ""

#: ../channels/form.rst:162
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:165
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:170
msgid ""
"``<script src=\"https://code.jquery.com/jquery-3.6.0.min.js\"></script>``"
msgstr ""

#: ../channels/form.rst:174
msgid "Do not mix jQuery versions - it's likely to break something."
msgstr ""

#: ../channels/form.rst:192
msgid "Body section"
msgstr ""

#: ../channels/form.rst:177
msgid ""
"The second code block is the actual code required for your form to run. It "
"is updated automatically when changing settings in the designer above."
msgstr ""

#: ../channels/form.rst:181
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:185
msgid ""
"The rest can either be placed at the same level or somewhere else on the "
"same page."
msgstr ""

#: ../channels/form.rst:190
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:194
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:203
msgid "Potential Spam Issue"
msgstr ""

#: ../channels/form.rst:205
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:209
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:213
msgid "Form settings to limit ticket creation"
msgstr ""

#: ../channels/form.rst:217
msgid "Option"
msgstr ""

#: ../channels/form.rst:218
msgid "Default value"
msgstr ""

#: ../channels/form.rst:219 ../manage/public-links.rst:47
#: ../misc/object-conditions/basics.rst:64 ../misc/variables.rst:100
#: ../system/core-workflows/condition-operators.rst:21
#: ../system/objects/permissions.rst:39 ../system/subscription.rst:208
msgid "Description"
msgstr ""

#: ../channels/form.rst:220
msgid "``form_ticket_create_by_ip_per_hour``"
msgstr ""

#: ../channels/form.rst:221
msgid "``20``"
msgstr ""

#: ../channels/form.rst:222
msgid "Limits ticket creation per IP and hour to 20 tickets"
msgstr ""

#: ../channels/form.rst:223
msgid "``form_ticket_create_by_ip_per_day``"
msgstr ""

#: ../channels/form.rst:224
msgid "``240``"
msgstr ""

#: ../channels/form.rst:225
msgid "Limits ticket creation per IP and day to 240 tickets"
msgstr ""

#: ../channels/form.rst:226
msgid "``form_ticket_create_per_day``"
msgstr ""

#: ../channels/form.rst:227
msgid "``5000``"
msgstr ""

#: ../channels/form.rst:228
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:238
msgid "**Change the ticket creation per IP and hour to 10**::"
msgstr ""

#: ../channels/form.rst:242
msgid "**Change the ticket creation per IP and hour to 50**::"
msgstr ""

#: ../channels/form.rst:246
msgid "**Change the ticket creation per day to 500**::"
msgstr ""

#: ../channels/form.rst:252
msgid "Further Options to Make it Harder"
msgstr ""

#: ../channels/form.rst:254
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:258
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:262
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/managing-accounts.rst:2
msgid ""
"Managing accounts in Google channels works nearly identically as for email "
"channels. This is why the section has been adopted almost verbatim from :doc:"
"`here </channels/email/accounts/managing-accounts>`."
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 <google-folder>` 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/secondary-addresses.rst:3
msgid ""
"Secondary addresses for accounts in Google channels work the same way as in "
"email channels. This is why the section has been adopted verbatim from :doc:"
"`here </channels/email/accounts/secondary-addresses>`."
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/basic-setup.rst:2
msgid "Basic Setup"
msgstr ""

#: ../channels/google/basic-setup.rst:4
msgid ""
"To set up a new Gmail or G Suite channel in Zammad, you first have to create "
"an **OAuth app** in Google's Cloud console. Then you can connect Zammad with "
"your Google account and add as many Gmail accounts to Zammad as you want, "
"using only active Gmail browser sessions (no usernames or passwords "
"required)."
msgstr ""

#: ../channels/google/basic-setup.rst:10
msgid ""
"If you already set up Google email channels in Zammad, you can easily "
"migrate them to a Google channel. Follow the steps below but skip the step "
"\"Add Account\" and proceed with :ref:`migrate-channel`."
msgstr ""

#: ../channels/google/basic-setup.rst:17
#: ../channels/microsoft365/accounts/register-app.rst:2
msgid "Register an OAuth App"
msgstr ""

#: ../channels/google/basic-setup.rst:19
msgid ""
"Sign in to the `Google Cloud console <https://console.cloud.google.com/>`_. "
"You should see a dashboard where you can add a new project. If you already "
"have an app which is in production, create a new one and follow the steps "
"below."
msgstr ""

#: ../channels/google/basic-setup.rst:25
msgid "Create an OAuth Consent Screen"
msgstr ""

#: ../channels/google/basic-setup.rst:27
msgid ""
"In the left sidebar of your project's \"APIs & Services\" section, select "
"OAuth consent screen and provide the requested information."
msgstr ""

#: ../channels/google/basic-setup.rst:None
msgid "Screenshot shows OAuth consent screen creation in Google Cloud console"
msgstr ""

#: ../channels/google/basic-setup.rst:33
msgid ""
"In the first screen, select \"Internal\" as User Type and click on "
"\"Create\"."
msgstr ""

#: ../channels/google/basic-setup.rst:35
msgid "Provide the following information in the next screen:"
msgstr ""

#: ../channels/google/basic-setup.rst:37
msgid "**App name**: enter a suitable name for this app"
msgstr ""

#: ../channels/google/basic-setup.rst:38
msgid "**User support email**: select an email address from the dropdown"
msgstr ""

#: ../channels/google/basic-setup.rst:39
msgid ""
"**Authorized domain**: the domain of your Zammad without http or https prefix"
msgstr ""

#: ../channels/google/basic-setup.rst:40
msgid "**Developer contact information**: enter a valid email address"
msgstr ""

#: ../channels/google/basic-setup.rst:42
msgid ""
"After entering the information, click on \"Save and Continue\". You should "
"be on the \"Scopes\" screen. Click on \"Add or Remove Scopes\" to see the "
"dialog as in the following screenshot."
msgstr ""

#: ../channels/google/basic-setup.rst:None
msgid "Screenshot with highlighted API selection"
msgstr ""

#: ../channels/google/basic-setup.rst:51
msgid ""
"Enter ``https://mail.google.com`` in the \"Manually add scopes\" text field"
msgstr ""

#: ../channels/google/basic-setup.rst:52
msgid ""
"Click on \"Add to Table\" to have it in the selectable scopes table above"
msgstr ""

#: ../channels/google/basic-setup.rst:53
msgid "Select it by checking the box"
msgstr ""

#: ../channels/google/basic-setup.rst:54
msgid "Confirm by clicking the \"Update\" button"
msgstr ""

#: ../channels/google/basic-setup.rst:56
msgid ""
"Go on by clicking \"Save and Continue\". If your app is in \"Testing\" mode, "
"add a user as which you want to sign in to your Google account. After that "
"you see a summary screen where you can check the information. Confirm by "
"clicking the \"Back to Dashboard\" button and go on with creating "
"credentials for your app."
msgstr ""

#: ../channels/google/basic-setup.rst:63
msgid "Create Credentials"
msgstr ""

#: ../channels/google/basic-setup.rst:65
msgid ""
"Select \"Credentials\" in the left sidebar, click on \"➕ Create "
"Credentials\" and choose \"OAuth client ID\"."
msgstr ""

#: ../channels/google/basic-setup.rst:None
msgid "Screenshot shows credentials screen with highlighted elements"
msgstr ""

#: ../channels/google/basic-setup.rst:72
msgid ""
"Select \"Web application\" as Application type, give it a name and enter "
"your redirect URL."
msgstr ""

#: ../channels/google/basic-setup.rst:79
msgid ""
"The redirect URL is basically the domain of your Zammad instance, extended "
"with ``/api/v1/external_credentials/google/callback``."
msgstr ""

#: ../channels/google/basic-setup.rst:82
msgid ""
"You can even find the complete redirect URL in Zammad's admin area under "
"Channels > Google. Click on \"Configure App\" and find your URL under \"Your "
"callback URL\"."
msgstr ""

#: ../channels/google/basic-setup.rst:None
msgid "Screenshot shows Zammad's configuration dialog for a Google app"
msgstr ""

#: ../channels/google/basic-setup.rst:91
msgid ""
"Click on \"Create\" after inserting the information. You will see a dialog "
"with your client ID and client secret. You need both of them in the next "
"step for configuring Zammad to connect it to Google."
msgstr ""

#: ../channels/google/basic-setup.rst:96
msgid "Configure App"
msgstr ""

#: ../channels/google/basic-setup.rst:98
msgid ""
"Go to Channels > Google in Zammad's admin area and click on \"Configure "
"App\". Insert the client ID and client secret which you got in the step "
"before."
msgstr ""

#: ../channels/google/basic-setup.rst:None
msgid ""
"Screenshot shows dialogs from Google and Zammad with client ID and secret"
msgstr ""

#: ../channels/google/basic-setup.rst:106
msgid ""
"Confirm by clicking the \"Submit\" button. Now you can add a Google account "
"as channel in Zammad, see next step."
msgstr ""

#: ../channels/google/basic-setup.rst:110
#: ../channels/microsoft365-graph/accounts.rst:121
msgid "Add Account"
msgstr ""

#: ../channels/google/basic-setup.rst:112
msgid ""
"If you already have Google email channels, you can skip this step and head "
"over to :ref:`migrate-channel`."
msgstr ""

#: ../channels/google/basic-setup.rst:115
msgid ""
"After you've registered Zammad as an OAuth app, you can connect Gmail "
"accounts to Zammad."
msgstr ""

#: ../channels/google/basic-setup.rst:122
msgid ""
"By default, Zammad will **delete all emails** in your inbox during the "
"import process. Use the *Keep Messages on Server* setting to :ref:`disable "
"this behavior <google-keep-messages-on-server>`."
msgstr ""

#: ../channels/google/basic-setup.rst:125
msgid ""
"Zammad will send an auto-reply message to every email it imports (including "
"the old ones!). Make sure to :doc:`disable this behavior </manage/trigger>` "
"prior adding an email account and to turn it back on once all your messages "
"have been imported."
msgstr ""

#: ../channels/google/basic-setup.rst:131
msgid ""
"To connect you Google account, click on \"Add Account\" in Zammad. You will "
"be redirected to a consent dialog. Click through the screens and and make "
"sure to select the desired Google account as well as to grant the permission "
"for email handling as you can see in the following screenshot."
msgstr ""

#: ../channels/google/basic-setup.rst:None
msgid "Screenshot shows Google's consent screen with checked email permission"
msgstr ""

#: ../channels/google/basic-setup.rst:141
msgid ""
"After clicking on \"Continue\", you are redirected to Zammad where you can "
"see a dialog for specifying some settings for the channel:"
msgstr ""

#: ../channels/google/basic-setup.rst:None
msgid "Screenshot shows Zammad's add channel dialog"
msgstr ""

#: ../channels/google/basic-setup.rst:153
msgid ""
"Use :doc:`filters </channels/google/filters>` for more fine-grained sorting "
"of incoming email."
msgstr ""

#: ../channels/google/basic-setup.rst:160
#: ../channels/microsoft365/accounts/account-setup.rst:102
msgid ""
"**Change to ...** will add this email address to the group for outgoing "
"emails. This may overwrite an already assigned email address."
msgstr ""

#: ../channels/google/basic-setup.rst:163
msgid ""
"**Do not change email address** doesn't assign an email address to the group "
"or change it. If the group has no assigned email address, it stays empty. If "
"the group already has an assigned email address, it stays the same."
msgstr ""

#: ../channels/google/basic-setup.rst:170
msgid ""
"Specify which folder (or *label*) to fetch from, or leave empty to fetch "
"from ``INBOX``. If specifying a nested folder, be sure to use the full path, "
"e.g. ``Inquiries/Tech-Support``."
msgstr ""

#: ../channels/google/basic-setup.rst:200
msgid ""
"After successfully adding the Google account, you can adjust the default "
"group Zammad is going to assign incoming new tickets to."
msgstr ""

#: ../channels/google/basic-setup.rst:214
msgid "Migrate from Email Channel"
msgstr ""

#: ../channels/google/basic-setup.rst:217
msgid "Convert Email Channel to Google Channel"
msgstr ""

#: ../channels/google/basic-setup.rst:219
msgid ""
"Zammad provides a migration logic that allows you to migrate existing Google "
"accounts from an email channel into a Google channel."
msgstr ""

#: ../channels/google/basic-setup.rst:222
#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:10
msgid "🧐 **Zammad is expecting specific settings**"
msgstr ""

#: ../channels/google/basic-setup.rst:224
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/basic-setup.rst:227
msgid ""
"The easiest way to start the migration is to :ref:`register-oauth-google` "
"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/basic-setup.rst:231
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/basic-setup.rst:235
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/basic-setup.rst:None ../channels/google/basic-setup.rst:0
msgid "Migrate an existing email channel to Google"
msgstr ""

#: ../channels/google/basic-setup.rst:243
#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:29
msgid "Rolling Back the Migration"
msgstr ""

#: ../channels/google/basic-setup.rst:245
#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:31
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/basic-setup.rst:260
msgid "My OAuth credentials stopped working"
msgstr ""

#: ../channels/google/basic-setup.rst:259
msgid ""
"Did you recently change your Google password? Google invalidates all your "
"OAuth tokens whenever you change it."
msgstr ""

#: ../channels/google/basic-setup.rst:274
msgid "How to use the Gmail account for outgoing system notifications?"
msgstr ""

#: ../channels/google/basic-setup.rst:263
msgid ""
"On **subscription/cloud-hosted instances**, you can't do that. Notifications "
"will always come from “Notification Master <noreply\\@your.zammad.domain>”."
msgstr ""

#: ../channels/google/basic-setup.rst:267
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 <https://support.google.com/a/answer/166852>`_ can "
"have their accounts suspended."
msgstr ""

#: ../channels/google/basic-setup.rst:273
msgid ""
"Set up a generic :doc:`email channel </channels/email/index>` instead and "
"use the :ref:`Email Notification <email-notification>` setting."
msgstr ""

#: ../channels/google/basic-setup.rst:277
msgid "I successfully added my account, but Zammad isn't fetching new emails"
msgstr ""

#: ../channels/google/basic-setup.rst:277
msgid ""
"If you specified a :ref:`custom folder/label to fetch from <google-folder>`, "
"are you sure incoming mail is arriving in that folder?"
msgstr ""

#: ../channels/google/email-headers.rst:3
msgid ""
"Header based actions in Google channels work in the same way as in email "
"channels. This is why the section has been adopted verbatim from :doc:`here "
"</channels/email/email-headers>`."
msgstr ""

#: ../channels/google/filters.rst:3
msgid ""
"Filters in Google channels work in the same way as filters in email "
"channels. This is why the section has been adopted verbatim from :doc:`here "
"</channels/email/filters>`."
msgstr ""

#: ../channels/google/filters/system-filters.rst:3
msgid ""
"System Filters in Google channels work in the same way as in email channels. "
"This is why the section has been adopted verbatim from :doc:`here </channels/"
"email/filters/system-filters>`."
msgstr ""

#: ../channels/google/index.rst:2
msgid "Google Email"
msgstr ""

#: ../channels/google/index.rst:15
msgid "Connect a Google Email account to Zammad."
msgstr ""

#: ../channels/google/index.rst:None
msgid "Google channel settings panel"
msgstr ""

#: ../channels/google/index.rst:21
msgid ""
"Google channels are a specialized kind of :doc:`📨 email channel </channels/"
"email/index>`."
msgstr ""

#: ../channels/google/index.rst:24
msgid ""
"If you're already familiar with email channels, you can skip most of this. "
"However, you should have a look at the :doc:`./basic-setup` to get started."
msgstr ""

#: ../channels/google/index.rst:32
msgid ":doc:`basic-setup`"
msgstr ""

#: ../channels/google/index.rst:29
msgid "Connect Zammad to Google and add an account to fetch emails from."
msgstr ""

#: ../channels/google/index.rst:31
msgid ""
"Self-hosted users may have already completed this step during new system "
"setup."
msgstr ""

#: ../channels/google/index.rst:36
msgid ":doc:`Filters <filters>`"
msgstr ""

#: ../channels/google/index.rst:35
msgid ""
"Make sure new tickets show up in the right place with automated, if-this-"
"then-that rules for all incoming email."
msgstr ""

#: ../channels/google/index.rst:39
msgid ":doc:`Signatures <signatures>`"
msgstr ""

#: ../channels/google/index.rst:39
msgid "Customize signatures for all outgoing emails."
msgstr ""

#: ../channels/google/index.rst:46
msgid ":doc:`Settings <settings>`"
msgstr ""

#: ../channels/google/index.rst:50
msgid ":doc:`Header based actions <email-headers>`"
msgstr ""

#: ../channels/google/settings.rst:3
msgid ""
"Settings in Google channels work in the same way as in email channels. This "
"is why the section has been adopted verbatim from :doc:`here </channels/"
"email/settings>`."
msgstr ""

#: ../channels/google/signatures.rst:3
msgid ""
"Signatures in Google channels work in the same way as in email channels. "
"This is why the section has been adopted verbatim from :doc:`here </channels/"
"email/signatures>`."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:4
msgid ""
"You can connect to user and shared mailboxes in your M365 environment. "
"Follow the steps below and skip not applicable parts."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:8 ../misc/first-steps.rst:2
msgid "First Steps"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:10
#: ../channels/microsoft365/accounts/register-app.rst:18
msgid ""
"Check your FQDN under *Settings > System > Fully Qualified Domain Name* in "
"the admin interface of Zammad. If it is not correct, change it now. "
"Otherwise the setup of the channel will fail."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:13
msgid ""
"Go to *Channels > Microsoft 365 Graph Email* and click on **Connect "
"Microsoft 365 App**. Copy the provided callback URL."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:19
msgid ""
"Go to Microsoft's `Entra admin center <https://entra.microsoft.com/#home>`_ "
"and log in as an administrator (at least application administrator "
"permission is required)."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:24
#: ../channels/microsoft365/accounts/register-app.rst:33
#: ../settings/security/third-party/facebook.rst:None
msgid "Create App"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:None
#: ../channels/microsoft365/accounts/register-app.rst:None
msgid ""
"Screenshot shows Entra admin center with application registration screen."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:30
#: ../channels/microsoft365/accounts/register-app.rst:39
msgid ""
"Create a new app by going to *Applications > App registrations* and select "
"**New registration**."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:32
#: ../channels/microsoft365/accounts/register-app.rst:41
msgid "Enter a fitting name and select an account type. Supported types are:"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:34
#: ../channels/microsoft365/accounts/register-app.rst:43
msgid "Accounts in this organizational directory only (Single tenant)"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:35
#: ../channels/microsoft365/accounts/register-app.rst:44
msgid "Accounts in any organizational directory (Multitenant)"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:37
#: ../channels/microsoft365/accounts/register-app.rst:50
msgid ""
"Under \"Redirect URI\", select \"Web\" as platform and paste your already "
"copied callback URL from Zammad."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:39
#: ../channels/microsoft365/accounts/register-app.rst:52
msgid "Click on **Register**."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:None
msgid "Screenshot shows Entra admin center with application overview screen."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:46
msgid ""
"In the overview screen, copy the \"Application (client) ID\", switch to "
"Zammad and paste it in the \"Client ID\" field in the pop up."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:48
msgid ""
"Only required for single tenant setup: copy the \"Directory (tenant) ID\" "
"and paste it in the \"Tenant UUID/Name\" field in Zammad."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:52
#: ../channels/microsoft365/accounts/register-app.rst:55
msgid "Create Secret"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:None
#: ../channels/microsoft365/accounts/register-app.rst:None
msgid "Screenshot shows Entra admin center with client secret screen."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:58
#: ../channels/microsoft365/accounts/register-app.rst:61
msgid ""
"In Entra, go to \"Certificates & secrets\" and add a secret by clicking the "
"**New client secret** button."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:60
#: ../channels/microsoft365/accounts/register-app.rst:63
msgid "Enter a description, set an expiry duration and click **Add**."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:61
#: ../channels/microsoft365/accounts/register-app.rst:64
msgid ""
"Copy the string under \"Value\", this is the secret. Paste it to Zammad in "
"the \"Client Secret\" field."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:65
#: ../channels/microsoft365/accounts/register-app.rst:68
msgid "Configure API Permissions"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:None
#: ../channels/microsoft365/accounts/register-app.rst:None
msgid "Screenshot shows Entra admin center with api permission screen."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:71
#: ../channels/microsoft365/accounts/register-app.rst:74
msgid "Go to \"API permissions\" and **Add a permission**."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:72
#: ../channels/microsoft365/accounts/register-app.rst:75
msgid "Select \"Microsoft Graph\" and \"Delegated permissions\"."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:73
#: ../channels/microsoft365/accounts/register-app.rst:76
msgid "Add the following permissions:"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:75
#: ../channels/microsoft365/accounts/register-app.rst:81
msgid "``offline_access``"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:76
#: ../channels/microsoft365/accounts/register-app.rst:79
#: ../settings/security/third-party/microsoft.rst:67
msgid "``openid``"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:77
#: ../channels/microsoft365/accounts/register-app.rst:80
msgid "``profile``"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:78
msgid "``Mail.ReadWrite``"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:79
msgid "``Mail.Send``"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:80
msgid "``Mail.ReadWrite.Shared``"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:81
msgid "``Mail.Send.Shared``"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:83
#: ../channels/microsoft365/accounts/register-app.rst:85
msgid "Save it by clicking the **Add permissions** button."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:86
msgid "Additional Steps for Shared Mailboxes"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:88
msgid ""
"If you want to fetch email from a shared mailbox, you have to perform "
"additional steps:"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:91
msgid ""
"Log in to the `Exchange admin center <https://admin.exchange.microsoft."
"com>`_."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:92
msgid ""
"Go to *Recipients > Mailboxes*, select the mailbox and click on **Mailboxes "
"delegation**."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:94
msgid ""
"Under \"Send as\", click on **Edit** and **Add members**. Search and select "
"the user from which you want to access the mailbox and **Save** it."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:96
msgid "Do the same for \"Read and manage (Full Access)\"."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:100
msgid "Configure the Channel in Zammad"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:103
#: ../channels/microsoft365/accounts/register-app.rst:140
msgid "App Configuration"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:None
msgid "Screenshot shows Zammad's app configuration dialog."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:109
msgid ""
"If you followed this guide, you already should have pasted your app "
"information. If not, here is a short summary:"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:112
#: ../channels/microsoft365/accounts/register-app.rst:146
msgid "In Zammad's channel configuration, click on **Configure App**."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:113
#: ../channels/microsoft365/accounts/register-app.rst:147
msgid "Enter your app details:"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:115
#: ../channels/microsoft365/accounts/register-app.rst:149
msgid "Client ID: *Application (client) ID*"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:116
#: ../channels/microsoft365/accounts/register-app.rst:150
msgid "Client Secret: *Value* from client secret"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:117
#: ../channels/microsoft365/accounts/register-app.rst:151
msgid ""
"Tenant UUID/Name: *Directory (tenant) ID* (not required for shared mailboxes)"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:118
#: ../channels/microsoft365/accounts/register-app.rst:152
msgid "Click on **Submit**."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:123
msgid ""
"Now you can add your account to Zammad. Do so by clicking the **Add "
"account** button in the top right corner. Select the correct mailbox type. "
"In case you selected \"Shared Mailbox\", you have to enter the email address "
"of the shared mailbox. Confirm by clicking the **Authenticate** button, "
"enter your credentials and confirm the requested permissions by clicking the "
"**Accept** button."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:None
msgid "Screenshot shows Zammad's dialog for account configuration."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:133
msgid ""
"After that, Zammad will ask you to assign a destination group. Select a "
"group which should (initially) handle the incoming tickets of this channel. "
"Additionally, you can decide if assign the email address should be assigned "
"to the selected group for outgoing emails (*Destination group > Sending "
"email address*). Choose between:"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:139
msgid ""
"**Change to ...** to add this email address to the group for outgoing "
"emails. This may overwrite an already assigned email address."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:142
msgid ""
"**Do not change email address** if you don't want assign an email address to "
"the group or change it. If the group has no assigned email address, it stays "
"empty. If the group already has an assigned email address, it stays the same."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:146
msgid ""
"You can also specify a folder from which Zammad should fetch emails from. If "
"you do so, make sure that the emails are routed to this folder somehow. "
"Otherwise, you won't receive tickets. Leave it empty to fetch all emails "
"from the inbox. After that, choose if fetched emails should remain on the "
"server or not."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:152
msgid ""
"Depending if there are already email messages in this account, the archive "
"mode dialog may be shown."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:157
msgid ""
"Now your channel is ready and can be used! If something doesn't work, have a "
"look at the :doc:`common errors section <common-errors>`, where you can find "
"common errors related to the M365 configuration."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:161
#: ../channels/microsoft365/accounts.rst:39
msgid ""
"🤔 **How do I use my Microsoft 365 account for outgoing system notifications?"
"**"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:163
#: ../channels/microsoft365/accounts.rst:41
msgid ""
"On **subscription/cloud-hosted instances**, you can't. Notifications will "
"always come from “Notification Master <noreply\\@your.zammad.domain>”."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:167
#: ../channels/microsoft365/accounts.rst:45
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 <https://docs.microsoft.com/en-us/"
"office365/servicedescriptions/exchange-online-service-description/exchange-"
"online-limits#receiving-and-sending-limits>`_ can have their accounts "
"suspended."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:173
#: ../channels/microsoft365/accounts.rst:51
msgid ""
"Set up a generic :doc:`email channel </channels/email/index>` instead, then "
"use the :ref:`Email Notification <email-notification>` setting."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:177
msgid "Re-Authenticate"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:179
msgid ""
"If your token got invalid, you have to replace the token due to other "
"reasons, you want to use a shared mailbox with another user, you can use the "
"**Re-Authenticate** button."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:183
msgid ""
"In case you are using an user mailbox, the new user has to match the "
"existing one, otherwise it will result in a user mismatch error. In this "
"case, you should delete the channel and add a new account."
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:188
#: ../channels/microsoft365/common-errors.rst:71
msgid "Request Admin Consent"
msgstr ""

#: ../channels/microsoft365-graph/accounts.rst:190
msgid ""
"It is possible to request the permissions via admin consent. In this case "
"Zammad will request necessary permissions for you from your admin, and then "
"your admin (if it's not the same user as you) can accept them on Microsoft "
"side. Trigger this process via the **Request Admin Consent** button in "
"Zammad."
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:2
#: ../channels/microsoft365/common-errors.rst:2
msgid "Common Errors"
msgstr ""

#: ../channels/microsoft365-graph/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 </channels/microsoft365-graph/index>` "
"for the configuration and the :doc:`common errors mentioned in the M365 IMAP "
"channel <../microsoft365/common-errors>`, if your error is not covered here."
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:12
msgid ""
"If you try to fix a problem, make sure to remove the account after the fix "
"first and re-add it then again."
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:16
msgid "Problem with User Mailbox"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:19
msgid "``MailboxNotEnabledForRESTAPI``"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:19
msgid ""
"*The mailbox is either inactive, soft-deleted, or is hosted on-premise.*"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:21
msgid "Possible reasons:"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:23
msgid "The user has no access to the mailbox."
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:24
msgid "The account has no mailbox at all (user mailboxes)."
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:26
msgid ""
"Either grant the user access to the mailbox or assign them a license and "
"create a mailbox for this user."
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:30
msgid "Problem with User Permissions"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:33
msgid "``ErrorItemNotFound``"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:33
msgid ""
"*The specified object was not found in the store., Default folder Root not "
"found.*"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:35
msgid ""
"Indicates that the user has no delegation permissions for the mailbox. Make "
"sure that the permissions are set correctly or consider using another "
"account."
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:40
msgid "Problem with Shared Mailbox"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:43
msgid "``ErrorInvalidUser``"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:43
msgid "*The requested user '\\*' is invalid.*"
msgstr ""

#: ../channels/microsoft365-graph/common-errors.rst:45
msgid ""
"Possible reason could be that the shared mailbox you provided is wrong. "
"Check if the provided shared mailbox email address is correct."
msgstr ""

#: ../channels/microsoft365-graph/email-headers.rst:3
#: ../channels/microsoft365/email-headers.rst:3
msgid ""
"Header based actions in Microsoft 365 channels work in the same way as in "
"email channels. This is why the section has been adopted verbatim from :doc:"
"`here </channels/email/email-headers>`."
msgstr ""

#: ../channels/microsoft365-graph/filters.rst:3
#: ../channels/microsoft365/filters.rst:3
msgid ""
"Filters in Microsoft 365 channels work in the same way as in email channels. "
"This is why the section has been adopted verbatim from :doc:`here </channels/"
"email/filters>`."
msgstr ""

#: ../channels/microsoft365-graph/filters/system-filters.rst:3
#: ../channels/microsoft365/filters/system-filters.rst:3
msgid ""
"System Filters in Microsoft 365 channels work in the same way as in email "
"channels. This is why the section has been adopted verbatim from :doc:`here "
"</channels/email/filters/system-filters>`."
msgstr ""

#: ../channels/microsoft365-graph/index.rst:2
msgid "Microsoft 365 Graph Email"
msgstr ""

#: ../channels/microsoft365-graph/index.rst:14
msgid ""
"Connect a Microsoft 365 account (formerly \"Office 365\") via Graph API to "
"Zammad."
msgstr ""

#: ../includes/m365-imap-graph.rst:4
msgid ""
"What is the difference between the :doc:`Graph-API- </channels/microsoft365-"
"graph/index>` and :doc:`IMAP-based M365 channel </channels/microsoft365/"
"index>`?"
msgstr ""

#: ../includes/m365-imap-graph.rst:8
msgid "The Graph-API variant has some advantages over the IMAP-based channel:"
msgstr ""

#: ../includes/m365-imap-graph.rst:10
msgid ""
"Shared mailboxes are implemented in a better way. By using them, you can "
"save some license costs."
msgstr ""

#: ../includes/m365-imap-graph.rst:12
msgid ""
"The selection of an inbox folder is implemented with a tree-select field in "
"Zammad. So you can choose a folder from the fetched folder list, which is "
"much less error-prone."
msgstr ""

#: ../includes/m365-imap-graph.rst:15
msgid "It is the future-proof way of connecting to your M365 environment."
msgstr ""

#: ../includes/m365-imap-graph.rst:16
msgid "It is more secure and scalable and offers a unified endpoint."
msgstr ""

#: ../includes/m365-imap-graph.rst:18
msgid ""
"So, if you are in doubt which one to use, we recommend using the Graph "
"channel."
msgstr ""

#: ../channels/microsoft365-graph/index.rst:22
#: ../channels/microsoft365/index.rst:22
msgid ""
"Microsoft 365 channels are a specialized kind of :doc:`📨 email channel </"
"channels/email/index>`."
msgstr ""

#: ../channels/microsoft365-graph/index.rst:25
#: ../channels/microsoft365/index.rst:25
msgid ""
"This documentation part does not cover :doc:`🗝 user authentication </"
"settings/security/third-party/microsoft>`."
msgstr ""

#: ../channels/microsoft365-graph/index.rst:28
#: ../channels/microsoft365/index.rst:28
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-graph/index.rst:36
#: ../channels/microsoft365/index.rst:36
msgid ":doc:`🛟 Common M365 errors </channels/microsoft365/common-errors>`"
msgstr ""

#: ../channels/microsoft365-graph/index.rst:37
#: ../channels/microsoft365/index.rst:37
msgid "Here you can find common errors and how to fix them."
msgstr ""

#: ../channels/microsoft365-graph/settings.rst:3
#: ../channels/microsoft365/settings.rst:3
msgid ""
"Settings in Microsoft 365 channels work in the same way as in email "
"channels. This is why the section has been adopted verbatim from :doc:`here "
"</channels/email/settings>`."
msgstr ""

#: ../channels/microsoft365-graph/signatures.rst:3
#: ../channels/microsoft365/signatures.rst:3
msgid ""
"Signatures in Microsoft 365 channels work in the same way as in email "
"channels. This is why the section has been adopted verbatim from :doc:`here "
"</channels/email/signatures>`."
msgstr ""

#: ../channels/microsoft365/accounts.rst:13
msgid ""
"Use the links below to step through the process of adding an M365 IMAP "
"channel to Zammad."
msgstr ""

#: ../channels/microsoft365/accounts.rst:20
msgid ":doc:`accounts/register-app`"
msgstr ""

#: ../channels/microsoft365/accounts.rst:17
msgid ""
"Use the **Connect Microsoft 365 App** dialog to register Zammad as an OAuth "
"app on Microsoft."
msgstr ""

#: ../channels/microsoft365/accounts.rst:20
msgid "This step is **required** before adding an account to Zammad."
msgstr ""

#: ../channels/microsoft365/accounts.rst:23
msgid "Use the **Add Account** dialog to connect your account."
msgstr ""

#: ../channels/microsoft365/accounts.rst:25
msgid "If you want to migrate an existing email channel, see next section."
msgstr ""

#: ../channels/microsoft365/accounts.rst:30
msgid ":doc:`accounts/migrate-from-email-channel`"
msgstr ""

#: ../channels/microsoft365/accounts.rst:28
msgid ""
"Migrate your existing email channels from standard IMAP to the dedicated "
"M365 IMAP channel in Zammad to quickly move your mailboxes. You can roll "
"back if something goes wrong!"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:4
msgid ""
"After you've :doc:`registered Zammad as an OAuth app <register-app>` in your "
"Entra admin center, you can begin connecting Microsoft accounts to Zammad."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:12
msgid ""
"By default, Zammad will **delete all emails** in your inbox during the "
"import process. Use the *Keep Messages on Server* setting to :ref:`disable "
"this behavior <microsoft365-keep-messages-on-server>`."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:15
msgid ""
"Zammad will **send an auto-reply message to every email it imports** "
"(including the old ones!). Make sure to :doc:`disable this behavior </manage/"
"trigger>` prior adding an email account, and to turn it back on once all "
"your messages have been imported."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:20
msgid "🤓 **Shared mailboxes are possible...**"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:22
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:27
msgid "🚛 Migrate an Existing Email Channel"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:29
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:34
msgid "Please refer the :doc:`migrate-from-email-channel` guide."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:37
msgid "Requesting Administrator Consent"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:39
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:54
msgid "Requesting the consent"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:45
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:48
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:51
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:65
msgid "Granting the consent (admin users)"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:57
msgid ""
"Within **Enterprise applications** in the Entra admin center, go to **Admin "
"consent requests**. You'll find all your user grant requests here."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:60
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:65
msgid ""
"After you've granted the request, continue with \"Add a New Account\" below."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:68
msgid "Add a New Account"
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:75
msgid ""
"Click **Add Account** to connect your Microsoft 365 accounts to Zammad. You "
"will be redirected to a Microsoft sign-in and confirmation page. Enter your "
"credentials and confirm it by clicking the **Accept** button."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:79
msgid "🕵️ **Aliases are not imported automatically.**"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:81
msgid "See :doc:`secondary-addresses` to add them yourself."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:None
msgid "Screenshot showing channel configuration during adding account for M365"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:95
msgid ""
"Use :doc:`filters </channels/microsoft365/filters>` for more fine-grained "
"sorting of incoming email."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:112
msgid ""
"Specify which folder (or *label*) to fetch from, or leave empty to fetch "
"from ``INBOX``."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:115
msgid ""
"If specifying a nested folder, be sure to use the full path; *e.g.,* "
"``Inquiries/Tech-Support``."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:123
msgid "``no`` Zammad deletes all imported messages"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:125
msgid "``yes`` Zammad marks imported messages as read"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:127
msgid ""
"(With this option, Zammad will only import unread messages. This means "
"Zammad may miss messages if the mailbox is externally modified.)"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:159
msgid "After adding the account"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:146
msgid ""
"After successfully adding the Microsoft 365 mail account, you can adjust the "
"default group Zammad is going to assign incoming new tickets to by clicking "
"the group name under \"Destination Group\":"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:155
msgid "Only **active** groups will be displayed."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:157
msgid ""
"Changing this setting will not reassign existing tickets to the new group."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:167
msgid "I successfully added my account, but Zammad isn't fetching new email"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:165
msgid ""
"If you specified a :ref:`custom folder/label to fetch from <microsoft365-"
"folder>`, are you sure incoming mail is arriving in that folder?"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:176
msgid ""
"My mailbox was working fine but suddenly it fails with ``EXPUNGE FAILED``"
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:170
msgid ""
"This is a Microsoft 365 specific issue which you have to solve with "
"Microsoft. However, you can have a look at `Microsofts documentation "
"<https://docs.microsoft.com/en-us/exchange/recipients-in-exchange-online/"
"manage-user-mailboxes/change-deleted-item-retention>`_ which might allow you "
"to solve the issue on your own."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:175
msgid ""
"As soon as the issue has been fixed, the Zammad channel will recover "
"automatically."
msgstr ""

#: ../channels/microsoft365/accounts/account-setup.rst:178
msgid ""
"Have a look at the :doc:`common errors section <../common-errors>` if you "
"still face issues with your M365 account."
msgstr ""

#: ../channels/microsoft365/accounts/managing-accounts.rst:3
msgid ""
"Managing accounts in Microsoft 365 channels works in the same way as in "
"email channels. This is why the section has been adopted verbatim from :doc:"
"`here </channels/email/accounts/managing-accounts>`."
msgstr ""

#: ../channels/microsoft365/accounts/managing-accounts.inbound-outbound.rst:5
msgid ""
"See :ref:`New Account Settings <microsoft365-folder>` for a detailed "
"description of each option."
msgstr ""

#: ../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/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:5
msgid "Migrate"
msgstr ""

#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:7
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:12
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:16
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:20
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:24
msgid ""
"After you pressed next you'll be redirect to Zammad's Microsoft 365 channel "
"overview. Your channel, if successful, is now migrated to a Microsoft 365 "
"IMAP channel."
msgstr ""

#: ../channels/microsoft365/accounts/migrate-from-email-channel.rst:0
msgid "Migrate an existing email channel to Microsoft 365"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:4
msgid ""
"Setting up a new Microsoft 365 account? Follow our basic setup guide to get "
"started."
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:7
msgid ""
"First, you'll have to connect Zammad to your Microsoft account as an **OAuth "
"app** in the Microsoft Entra 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
#: ../channels/whatsapp/preparation.rst:2
msgid "Preparation"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:21
msgid ""
"Go to *Channels > Microsoft 365 IMAP Email* and click on **Connect Microsoft "
"365 App**. Copy the provided callback URL."
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:25
msgid "Step-by-Step"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:27
msgid ""
"To get started, head over to `Microsoft's Entra Portal <https://entra."
"microsoft.com>`_. Make sure to use an admin account for your organization. "
"Otherwise, an admin will have to approve your changes before they can take "
"effect."
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:45
msgid ""
"Accounts in any organizational directory (Multitenant) and personal "
"Microsoft accounts (e.g. Skype, Xbox)"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:48
msgid "\"Personal Microsoft accounts only\" are not supported."
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:78
#: ../settings/security/third-party/saml/saml-keycloak.rst:23
#: ../settings/security/third-party/saml/saml-keycloak.rst:29
msgid "``email``"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:82
msgid "``IMAP.AccessAsUser.all``"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:83
msgid "``SMTP.Send``"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:88
msgid "Admin Consent (optional)"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:92
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:96
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:100
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:None
msgid "Screenshot showing enabled assignment requirement"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:108
msgid "Tightening your App (recommended, optional)"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:110
msgid ""
"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:114
msgid ""
"It also has another benefit: You can add the email account in question "
"immediately without any administrator being forced to step in manually."
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:118
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:123
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:130
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:135
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:None
msgid "Screenshot showing popup about connecting app"
msgstr ""

#: ../channels/microsoft365/accounts/register-app.rst:155
msgid ""
"🍾 Congratulations! Now you're ready to connect Microsoft 365 accounts to "
"Zammad."
msgstr ""

#: ../channels/microsoft365/accounts/secondary-addresses.rst:3
msgid ""
"Secondary addresses in Microsoft 365 channels work in the same way as in "
"email channels. This is why the section has been adopted verbatim from :doc:"
"`here </channels/email/accounts/secondary-addresses>`."
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 <https://account.live.com/names/"
"Manage>`_ 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 <https://outlook.office.com/ecp/>`_:"
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:4
msgid ""
"Here you can find some common errors in M365 context. Also have a look at "
"the general :doc:`M365 documentation </channels/microsoft365/index>` 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 </channels/microsoft365/accounts>` "
"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 </channels/microsoft365/accounts>` 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: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 </channels/"
"microsoft365/accounts/account-setup>` 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/common-errors.rst:160
msgid "Retrieval of Email Failed"
msgstr ""

#: ../channels/microsoft365/common-errors.rst:162
msgid ""
"**Error message:** Retrieval using the IMAP4 protocol failed for the "
"following message: [...]"
msgstr ""

#: ../channels/microsoft365/common-errors.rst:165
msgid ""
"This can be caused by Microsoft Defender for Office 365 when Zammad fetches "
"an email while its attachment is still being checked."
msgstr ""

#: ../channels/microsoft365/common-errors.rst:168
msgid ""
"To avoid this, you should change the `Safe Attachments unknown malware "
"response <https://learn.microsoft.com/en-us/defender-office-365/safe-"
"attachments-about?view=o365-worldwide#safe-attachments-policy-settings>`_ "
"from \"Dynamic Delivery\" to something else fitting your needs (e.g. "
"\"Block\") for your Office 365 instance."
msgstr ""

#: ../channels/microsoft365/common-errors.rst:175
msgid "Authentication Unsuccessful"
msgstr ""

#: ../channels/microsoft365/common-errors.rst:177
msgid "**Error message:** 535 5.7.3 Authentication unsuccessful"
msgstr ""

#: ../channels/microsoft365/common-errors.rst:179
msgid ""
"This error message can have different reasons. See description below for one "
"of them."
msgstr ""

#: ../channels/microsoft365/common-errors.rst:182
msgid ""
"Microsoft allows sign-in and authentication using the primary email address. "
"While this works for fetching emails, SMTP authentication may not work in "
"this case."
msgstr ""

#: ../channels/microsoft365/common-errors.rst:186
msgid ""
"Try to delete the MS account and recreate it using your username. In Zammad, "
"manually change the email address to the username. Then you should be able "
"to send and receive emails again."
msgstr ""

#: ../channels/microsoft365/index.rst:2
msgid "Microsoft 365 IMAP Email"
msgstr ""

#: ../channels/microsoft365/index.rst:14
msgid ""
"Connect a Microsoft 365 account (formerly \"Office 365\") via IMAP to Zammad."
msgstr ""

#: ../channels/sms.rst:2
msgid "SMS"
msgstr ""

#: ../channels/sms.rst:4
msgid ""
"SMS integration primarily lets you create tickets, add articles and respond "
"to tickets via SMS. It is also possible to send notifications, e.g. to "
"agents."
msgstr ""

#: ../channels/sms.rst:7
msgid ""
"You can configure SMS notifications in the admin interface under **Channels "
"> SMS**."
msgstr ""

#: ../channels/sms.rst:11
msgid "Configure Incoming SMS"
msgstr ""

#: ../channels/sms.rst:13
msgid ""
"MessageBird and Twilio are currently the only supported providers to process "
"incoming messages. Setting up the channel requires your account SID and an "
"authentication token. You can find an example for the Twilio configuration "
"in the following screenshots."
msgstr ""

#: ../channels/sms.rst:None
msgid "Twilio settings"
msgstr ""

#: ../channels/sms.rst:23
msgid "Enter these in the Zammad admin interface at SMS accounts."
msgstr ""

#: ../channels/sms.rst:None
msgid "Channel settings SMS"
msgstr ""

#: ../channels/sms.rst:30
msgid ""
"Further options are to enter a sender number and select a destination group. "
"The sender number is published when sending SMS from the ticket. Names can "
"also be entered. \"Destination group\" is relevant for incoming SMS that "
"can't be assigned to a specific ticket."
msgstr ""

#: ../channels/sms.rst:35
msgid ""
"After setting it all up, an SMS article could look like this in the ticket "
"view:"
msgstr ""

#: ../channels/sms.rst:41
msgid "Communication via SMS is available directly from inside Zammad."
msgstr ""

#: ../channels/sms.rst:44
msgid "Notifications via SMS"
msgstr ""

#: ../channels/sms.rst:46
msgid ""
"It's also possible to receive notifications via SMS. These are messages sent "
"by trigger or automation. Setup is done in the admin interface at **Channels "
"> SMS**."
msgstr ""

#: ../channels/sms.rst:50
msgid ""
"As service providers, Massenversand, MessageBird and Twilio are supported."
msgstr ""

#: ../channels/sms.rst:52
msgid ""
"Please specify the account ID and a token here. Furthermore it is possible "
"to enter a phone number or name to be shown to the recipient."
msgstr ""

#: ../channels/sms.rst:None
msgid "Notification settings"
msgstr ""

#: ../channels/sms.rst:59
msgid ""
"You can either save your configuration directly, or let your settings be "
"checked by running a test in advance."
msgstr ""

#: ../channels/sms.rst:62
msgid ""
"Now it's possible to send SMS notifications via trigger or automation. The "
"setup is done the same way as setting up :doc:`email notifications </"
"channels/email/accounts/email-notification>`. Please note that the user "
"object belonging to the person you want to notify must contain a mobile "
"phone number as an attribute. If there is no phone number registered, no SMS "
"will be sent."
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 <https://core.telegram."
"org/bots/api#getfile>`_."
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 <https://developer.twitter.com/en/"
"apply/user>`_."
msgstr ""

#: ../channels/twitter-x/twitter.rst:30
msgid ""
"`Create a new Twitter app <https://developer.twitter.com/en/apps/create>`_ "
"for Zammad."
msgstr ""

#: ../channels/twitter-x/twitter.rst:32
msgid ""
"Set your new app's permissions to *Read, write, and access direct messages.*"
msgstr ""

#: ../channels/twitter-x/twitter.rst:34
msgid "Generate a new access token & secret."
msgstr ""

#: ../channels/twitter-x/twitter.rst:35
msgid ""
"`Set up a dev environment <https://developer.twitter.com/en/account/"
"environments>`_ for the Account Activity API."
msgstr ""

#: ../channels/twitter-x/twitter.rst:37
msgid "Add your new Twitter app in Zammad."
msgstr ""

#: ../channels/twitter-x/twitter.rst:38
msgid "Add your Twitter account in Zammad."
msgstr ""

#: ../channels/twitter-x/twitter.rst:39
msgid ""
"Configure filters for creating new tickets based on **#tags** and "
"**@mentions**."
msgstr ""

#: ../channels/twitter-x/twitter.rst:42
msgid "Read on for details about each step."
msgstr ""

#: ../channels/twitter-x/twitter.rst:45
msgid "1. Apply for a Twitter Developer Account"
msgstr ""

#: ../channels/twitter-x/twitter.rst:51
msgid "Twitter Developer account: Welcome page"
msgstr ""

#: ../channels/twitter-x/twitter.rst:51
msgid ""
"This welcome page is displayed after completing the application for a "
"Developer account."
msgstr ""

#: ../channels/twitter-x/twitter.rst:54
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:57
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:69
msgid "2. Create a New Twitter App for Zammad"
msgstr ""

#: ../channels/twitter-x/twitter.rst:75
msgid "Twitter Developer account: Create app page"
msgstr ""

#: ../channels/twitter-x/twitter.rst:75
msgid ""
"To create a new app, select **Apps** under your user menu, then click "
"**Create an app**."
msgstr ""

#: ../channels/twitter-x/twitter.rst:78
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:84
msgid "App name"
msgstr ""

#: ../channels/twitter-x/twitter.rst:83
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:87
msgid "Application description"
msgstr ""

#: ../channels/twitter-x/twitter.rst:87
msgid "Anything is fine here."
msgstr ""

#: ../channels/twitter-x/twitter.rst:90
msgid "Website URL"
msgstr ""

#: ../channels/twitter-x/twitter.rst:90
msgid "The URL of your Zammad instance."
msgstr ""

#: ../channels/twitter-x/twitter.rst:96
msgid "Callback URLs"
msgstr ""

#: ../channels/twitter-x/twitter.rst:93
msgid ""
"``https://<zammad_instance>/api/v1/external_credentials/twitter/callback``"
msgstr ""

#: ../channels/twitter-x/twitter.rst:95
msgid ""
"This URL is also visible in the **Connect Twitter App** dialog of your "
"Zammad admin settings panel."
msgstr ""

#: ../channels/twitter-x/twitter.rst:102
msgid "Tell us how this app will be used"
msgstr ""

#: ../channels/twitter-x/twitter.rst:99
msgid "Anything is fine here. We suggest the following::"
msgstr ""

#: ../channels/twitter-x/twitter.rst:105
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:111
msgid "Select *Read, write, and access direct messages.*"
msgstr ""

#: ../channels/twitter-x/twitter.rst:114
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:120
msgid "You will need all four keys/tokens later, so don't close this tab."
msgstr ""

#: ../channels/twitter-x/twitter.rst:123
msgid "5. Set Up a Dev Environment"
msgstr ""

#: ../channels/twitter-x/twitter.rst:125
msgid ""
"After creating your app, `set up a dev environment`_ for the Account "
"Activity API."
msgstr ""

#: ../channels/twitter-x/twitter.rst:132
msgid "Twitter Developer account: Dev environments page"
msgstr ""

#: ../channels/twitter-x/twitter.rst:132
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:136
msgid "6. Add Your New Twitter App in Zammad"
msgstr ""

#: ../channels/twitter-x/twitter.rst:142
msgid "Zammad: Configure Twitter app"
msgstr ""

#: ../channels/twitter-x/twitter.rst:142
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:147
msgid "7. Add Your Twitter Account in Zammad"
msgstr ""

#: ../channels/twitter-x/twitter.rst:153
msgid "Zammad: Add Twitter account"
msgstr ""

#: ../channels/twitter-x/twitter.rst:153
msgid ""
"Click **Add Account** under **Channels > Twitter** in the admin settings "
"panel."
msgstr ""

#: ../channels/twitter-x/twitter.rst:160
msgid "Twitter: Authorize Zammad"
msgstr ""

#: ../channels/twitter-x/twitter.rst:160
msgid ""
"You will be redirected to Twitter and asked to authorize Zammad to access "
"your account."
msgstr ""

#: ../channels/twitter-x/twitter.rst:164
msgid "8. Configure Filters"
msgstr ""

#: ../channels/twitter-x/twitter.rst:170
msgid "Zammad: Configure Twitter accounts"
msgstr ""

#: ../channels/twitter-x/twitter.rst:170
msgid ""
"Set up filters to automatically create new tickets based on **#tags** or "
"**@mentions**."
msgstr ""

#: ../channels/twitter-x/twitter.rst:173
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:7
msgid ""
"If you even further want to configure what your customers can see and "
"select, you should have a look in our :doc:`/system/core-workflows` "
"documentation."
msgstr ""

#: ../channels/web.rst:None
msgid "The web channel settings page"
msgstr ""

#: ../channels/web.rst:15
msgid "Settings Affecting Your Customer"
msgstr ""

#: ../channels/web.rst:22
msgid "Enable Ticket creation"
msgstr ""

#: ../channels/web.rst:18
msgid ""
"You can forbid customers to create tickets via the web interface. This will "
"remove the \"➕\" button on the lower left. This does not forbid *updating* "
"existing tickets via UI."
msgstr ""

#: ../channels/web.rst:22 ../manage/public-links.rst:0
#: ../system/objects/types.rst:0
msgid "Default: ``yes``"
msgstr ""

#: ../channels/web.rst:34
msgid "Group selection for Ticket creation"
msgstr ""

#: ../channels/web.rst:25
msgid ""
"By default, your customers can create tickets in all groups. As this may be "
"unwanted, especially when having several support levels or internal groups, "
"you can select a set of groups you want to be selectable by your customers."
msgstr ""

#: ../channels/web.rst:30
msgid ""
"This does not affect your agents. Agents are affected by :doc:`/manage/"
"groups/access-levels`."
msgstr ""

#: ../channels/web.rst:33
msgid "Default: (empty selection)"
msgstr ""

#: ../channels/web.rst:37
msgid "Global Settings Affecting *All* Users"
msgstr ""

#: ../channels/web.rst:51
msgid "Tab behavior after ticket creation"
msgstr ""

#: ../channels/web.rst:40
msgid ""
"This setting allows administrators to provide a default behavior of Zammad's "
"tab *after* ticket update."
msgstr ""

#: ../channels/web.rst:43
msgid ""
"Users can always overrule this behavior. 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:47
msgid "Zammad remembers the decision of the user."
msgstr ""

#: ../channels/web.rst:49
msgid "Default: ``Stay on tab``"
msgstr ""

#: ../channels/web.rst:0
msgid "Ticket zoom with tab behavior to choose for the user"
msgstr ""

#: ../channels/whatsapp/index.rst:2
msgid "WhatsApp"
msgstr ""

#: ../channels/whatsapp/index.rst:4
msgid ""
"With the release of Zammad 6.3, you can now connect your Zammad with a "
"WhatsApp Business account, allowing your customers to reach out to you "
"through WhatsApp. 🎉"
msgstr ""

#: ../channels/whatsapp/index.rst:8
msgid ""
"If you already dived deep into this topic, you can head to the setup guide. "
"If not, we strongly encourage you to read the prerequisites and limitations "
"of this channel carefully and to follow our tutorial for preparing your "
"setup."
msgstr ""

#: ../channels/whatsapp/index.rst:13
msgid ""
"We tried to keep it clear and created a separate sub-page for the necessary "
"steps on Meta/WhatsApp side."
msgstr ""

#: ../channels/whatsapp/index.rst:17
msgid ""
"Please be aware that the usage of **WhatsApp Cloud API** is mandatory to "
"connect WhatsApp to Zammad. You won't be able to connect to WhatsApp in "
"Zammad if you just use the WhatsApp Business *App*. Have a look `here "
"<https://developers.facebook.com/docs/whatsapp/cloud-api>`_ for further "
"information about the Cloud API."
msgstr ""

#: ../channels/whatsapp/index.rst:24
msgid ""
"There may be additional costs for you from Meta/WhatsApp side. Have a look "
"at their `pricing page <https://developers.facebook.com/docs/whatsapp/"
"pricing>`_ to be safe from surprises."
msgstr ""

#: ../channels/whatsapp/index.rst:29
msgid ""
"Be aware that if you go through the whole process, it is very time "
"consuming. You should have some time to follow our preparation guide."
msgstr ""

#: ../channels/whatsapp/limitations.rst:4
msgid ""
"There are a number of limitations for this channel. Read them carefully."
msgstr ""

#: ../channels/whatsapp/limitations.rst:18
msgid "24-hour customer service window"
msgstr ""

#: ../channels/whatsapp/limitations.rst:7
msgid ""
"If a customer gets in touch with you via WhatsApp, a 24 hour window is "
"opened. Within this time window you can freely answer the question of the "
"customer. If the customer isn't replying, the service window will be "
"automatically closed after 24 hours. You will not be able to communicate "
"with this customer via WhatsApp due to their privacy policy and until a "
"fresh reply is received from your customer after the service window expires."
msgstr ""

#: ../channels/whatsapp/limitations.rst:14
msgid ""
"In case the ticket cannot be closed yet and in order to facilitate an "
"ongoing conversation, automatic reminders will be sent to the customer "
"asking them to reply and keep the service window open. They are sent 23 "
"hours after a message is received, and can be optionally deactivated in the "
"channel configuration."
msgstr ""

#: ../channels/whatsapp/limitations.rst:24
msgid "Customer-initiated communication only"
msgstr ""

#: ../channels/whatsapp/limitations.rst:21
msgid ""
"The WhatsApp channel only supports customer initiated communication. For "
"business-initiated communication, it would be necessary to create a message "
"template which has to be verified by Meta first which is currently not "
"supported by Zammad."
msgstr ""

#: ../channels/whatsapp/limitations.rst:28
msgid "Supported media types"
msgstr ""

#: ../channels/whatsapp/limitations.rst:27
msgid ""
"Currently text messages, documents, images, audio, videos and stickers are "
"supported."
msgstr ""

#: ../channels/whatsapp/limitations.rst:32
msgid "One attachment per article"
msgstr ""

#: ../channels/whatsapp/limitations.rst:31
msgid ""
"Currently, it's only possible to attach one file per outgoing message. It "
"has to be one of the supported media types (see above)."
msgstr ""

#: ../channels/whatsapp/limitations.rst:45
msgid "File size for attachments"
msgstr ""

#: ../channels/whatsapp/limitations.rst:35
msgid ""
"There are different maximum file sizes for different media types. To pick "
"the most important ones:"
msgstr ""

#: ../channels/whatsapp/limitations.rst:38
msgid "audio: 16 MB"
msgstr ""

#: ../channels/whatsapp/limitations.rst:39
msgid "document: 100 MB"
msgstr ""

#: ../channels/whatsapp/limitations.rst:40
msgid "image: 5 MB"
msgstr ""

#: ../channels/whatsapp/limitations.rst:41
msgid "video: 16 MB"
msgstr ""

#: ../channels/whatsapp/limitations.rst:42
msgid "sticker: 100/500 KB (static/animated)"
msgstr ""

#: ../channels/whatsapp/limitations.rst:44
msgid ""
"To read more in detail, have a look at their `documentation of supported "
"media types <https://developers.facebook.com/docs/whatsapp/cloud-api/"
"reference/media#supported-media-types>`_."
msgstr ""

#: ../channels/whatsapp/limitations.rst:49
msgid "One phone number per app"
msgstr ""

#: ../channels/whatsapp/limitations.rst:48
msgid ""
"If you want to use more than one phone number, you have to create a business "
"app for each number you want to use and add it as a separate channel in "
"Zammad."
msgstr ""

#: ../channels/whatsapp/preparation.rst:4
msgid ""
"Here you can find instructions for the required steps you need to take "
"before you can use the WhatsApp channel in Zammad."
msgstr ""

#: ../channels/whatsapp/preparation.rst:7
msgid ""
"Please note that these steps may change in the future, depending on changes "
"on Meta's side. You should also consider to read their docs if you have "
"issues:"
msgstr ""

#: ../channels/whatsapp/preparation.rst:10
msgid ""
"`WhatsApp Cloud API <https://developers.facebook.com/docs/whatsapp/cloud-"
"api>`_"
msgstr ""

#: ../channels/whatsapp/preparation.rst:11
msgid ""
"`WhatsApp Business Platform <https://developers.facebook.com/docs/whatsapp>`_"
msgstr ""

#: ../channels/whatsapp/preparation.rst:16
msgid "Create a Meta Business Account"
msgstr ""

#: ../channels/whatsapp/preparation.rst:18
msgid ""
"If you don't already have a business account, visit https://business."
"facebook.com/overview and click on \"Create an account\":"
msgstr ""

#: ../channels/whatsapp/preparation.rst:None
msgid "Meta business account starting page"
msgstr ""

#: ../channels/whatsapp/preparation.rst:25
msgid ""
"Have a look at `Meta's documentation <https://www.facebook.com/business/"
"help/1710077379203657?id=180505742745347>`_ if you have problems."
msgstr ""

#: ../channels/whatsapp/preparation.rst:31
msgid "Create a Meta Developer Account"
msgstr ""

#: ../channels/whatsapp/preparation.rst:33
msgid ""
"If you don't have a developer account already, go to https://developers."
"facebook.com/docs/development/register and register a new account."
msgstr ""

#: ../channels/whatsapp/preparation.rst:38
msgid "Create a Meta Developer App"
msgstr ""

#: ../channels/whatsapp/preparation.rst:40
msgid ""
"While already logged in with your developer account, go to https://"
"developers.facebook.com/apps/."
msgstr ""

#: ../channels/whatsapp/preparation.rst:43
msgid ""
"You will see a screen like the following screenshot. Click on \"Create App\" "
"and follow the steps below."
msgstr ""

#: ../channels/whatsapp/preparation.rst:None
msgid "Meta developer app overview"
msgstr ""

#: ../channels/whatsapp/preparation.rst:50
msgid "Choose \"Other\" when you are asked what you want to do with your app:"
msgstr ""

#: ../channels/whatsapp/preparation.rst:None
msgid "Meta app creation step 1"
msgstr ""

#: ../channels/whatsapp/preparation.rst:57
msgid "Choose \"Business\" as app type:"
msgstr ""

#: ../channels/whatsapp/preparation.rst:None
msgid "Meta app creation step 2"
msgstr ""

#: ../channels/whatsapp/preparation.rst:64
msgid ""
"Enter a name for the app, a contact email address and a business account. "
"Please note that the name may not contain specific product names from Meta, "
"as you can see in the screenshot below."
msgstr ""

#: ../channels/whatsapp/preparation.rst:73
msgid ""
"If you already have a business account, you should assign it. In this step, "
"this is optional, but later it is required anyway. Click on \"Create App\" "
"to finish this step."
msgstr ""

#: ../channels/whatsapp/preparation.rst:78
msgid "Add WhatsApp Product to Your App"
msgstr ""

#: ../channels/whatsapp/preparation.rst:80
msgid ""
"Now you have to add a product to your app. In our case, this is WhatsApp. "
"Search for it and click on \"Set up\":"
msgstr ""

#: ../channels/whatsapp/preparation.rst:87
msgid ""
"In the next step, you have to add a \"Meta Business Account\". This guide "
"assumes that you already have one. If not, go to the :ref:`instructions "
"above <create-meta-business-account>` and create one."
msgstr ""

#: ../channels/whatsapp/preparation.rst:None
msgid "Add the product WhatsApp to your app"
msgstr ""

#: ../channels/whatsapp/preparation.rst:97
msgid "Create a System User"
msgstr ""

#: ../channels/whatsapp/preparation.rst:98
msgid ""
"Go to `Users > System users <https://business.facebook.com/settings/system-"
"users/>`_ and add a system user. This is required to get a permanent API "
"token. Make sure the user has admin permissions."
msgstr ""

#: ../channels/whatsapp/preparation.rst:102
msgid ""
"After creating a system user, you should see a screen similar to the one "
"below. Here you can assign assets and (re-)generate an access token."
msgstr ""

#: ../channels/whatsapp/preparation.rst:105
msgid ""
"For now we just assign assets to this user. The creation of the token is "
"covered in the :doc:`Zammad setup section </channels/whatsapp/index>` "
"because the token is only displayed once and then you can copy and paste it "
"directly."
msgstr ""

#: ../channels/whatsapp/preparation.rst:None
msgid "System user overview"
msgstr ""

#: ../channels/whatsapp/preparation.rst:113
msgid ""
"You now have to assign assets to this user. Choose your app and \"Manage "
"app\" permissions:"
msgstr ""

#: ../channels/whatsapp/preparation.rst:None
msgid "Assign assets to system user"
msgstr ""

#: ../channels/whatsapp/preparation.rst:122
msgid "Configure Your WhatsApp Business Platform"
msgstr ""

#: ../channels/whatsapp/preparation.rst:124
msgid ""
"After adding a \"Meta Business Account\" to your app, the \"App Dashboard\" "
"is presented to you. Click on \"Start using the API\":"
msgstr ""

#: ../channels/whatsapp/preparation.rst:None
msgid "App dashboard overview"
msgstr ""

#: ../channels/whatsapp/preparation.rst:132
msgid "Assign an Unused Phone Number"
msgstr ""

#: ../channels/whatsapp/preparation.rst:134
msgid "Please note: this number may not be used in a WhatsApp app already!"
msgstr ""

#: ../channels/whatsapp/preparation.rst:None
msgid "Adding a new phone number to your app"
msgstr ""

#: ../channels/whatsapp/preparation.rst:140
msgid ""
"Click through the steps adding your information. You have to verify your "
"number by receiving a security code and repeating it when asked."
msgstr ""

#: ../channels/whatsapp/preparation.rst:143
msgid ""
"After you successfully performed these steps, you are now good to go with "
"the :doc:`setup on Zammad side <index>`. 🎉"
msgstr ""

#: ../channels/whatsapp/preparation.rst:146
msgid "We promise it will become easier! 🤓"
msgstr ""

#: ../channels/whatsapp/prerequisites.rst:4
msgid ""
"First, make sure you have followed our :doc:`preparation guide<preparation>`."
msgstr ""

#: ../channels/whatsapp/prerequisites.rst:6
msgid "Then, check if you meet the following requirements:"
msgstr ""

#: ../channels/whatsapp/prerequisites.rst:8
msgid ""
"Make sure your system is accessible from the internet because WhatsApp sends "
"messages via webhooks to your system."
msgstr ""

#: ../channels/whatsapp/prerequisites.rst:10
msgid ""
"Make sure to have properly setup your :doc:`FQDN in Settings > System </"
"settings/system/base>` (for the callback URL Meta will use to deliver new "
"messages)."
msgstr ""

#: ../channels/whatsapp/setup.rst:2 ../manage/knowledge-base.rst:36
#: ../system/integrations/github.rst:16 ../system/integrations/gitlab.rst:16
msgid "Setup"
msgstr ""

#: ../channels/whatsapp/setup.rst:4
msgid ""
"First of all, make sure to match the prerequisites and to read the "
"limitations above. If you did not setup your Meta Developer account, Meta "
"Business account and Meta Developer app, first go to our :doc:`preparation "
"page <preparation>` and come back here after finishing it."
msgstr ""

#: ../channels/whatsapp/setup.rst:9
msgid ""
"Then head over to Zammad's admin panel to add the WhatsApp channel under "
"\"Channels > WhatsApp > Add Account\" and follow the steps which are "
"described below."
msgstr ""

#: ../channels/whatsapp/setup.rst:14
msgid "Step 1"
msgstr ""

#: ../channels/whatsapp/setup.rst:16
msgid "In the first step you have to provide credentials of your account/app:"
msgstr ""

#: ../channels/whatsapp/setup.rst:None
msgid "Step 1 of adding a WhatsApp account"
msgstr ""

#: ../channels/whatsapp/setup.rst:29
msgid "WhatsApp Business Account ID"
msgstr ""

#: ../channels/whatsapp/setup.rst:24
msgid ""
"Enter your WhatsApp Business Account ID. You can find it in your app under "
"\"WhatsApp > API Setup\":"
msgstr ""

#: ../channels/whatsapp/setup.rst:0
msgid "App dashboard with business account ID"
msgstr ""

#: ../channels/whatsapp/setup.rst:49
msgid "Access Token"
msgstr ""

#: ../channels/whatsapp/setup.rst:32
msgid ""
"Enter the access token from your app. You can create it in the `business "
"settings <https://business.facebook.com/settings/system-users>`_ under "
"\"System Users\". The system user has to have \"Admin access\". Be aware "
"that you have to copy the token, it is just displayed once!"
msgstr ""

#: ../channels/whatsapp/setup.rst:0
msgid "Get your app token from the system user"
msgstr ""

#: ../channels/whatsapp/setup.rst:42
msgid ""
"Choose your created app, an expiration date of the token (we recommend "
"\"Never\") and the permissions ``whatsapp_business_management`` and "
"``whatsapp_business_messaging``:"
msgstr ""

#: ../channels/whatsapp/setup.rst:0
msgid "Create your app token"
msgstr ""

#: ../channels/whatsapp/setup.rst:59
msgid "App Secret"
msgstr ""

#: ../channels/whatsapp/setup.rst:52
msgid ""
"Enter your app secret. You can find it in your `app dashboard <https://"
"developers.facebook.com/apps/>`_ under \"App settings > Basic\" by clicking "
"on the \"Show\" button:"
msgstr ""

#: ../channels/whatsapp/setup.rst:0
msgid "App dashboard with app secret"
msgstr ""

#: ../channels/whatsapp/setup.rst:61
msgid ""
"After entering your data, click on **Next**. In the background, Zammad tries "
"to fetch your assigned phone number, which you can select in the next step."
msgstr ""

#: ../channels/whatsapp/setup.rst:65
msgid "Step 2"
msgstr ""

#: ../channels/whatsapp/setup.rst:67
msgid "The second step is about your phone number and messaging details:"
msgstr ""

#: ../channels/whatsapp/setup.rst:None
msgid "Step 2 of adding a WhatsApp account"
msgstr ""

#: ../channels/whatsapp/setup.rst:77
msgid "Phone Number"
msgstr ""

#: ../channels/whatsapp/setup.rst:75
msgid ""
"Choose the phone number you want to use for the channel. Zammad should have "
"fetched the numbers which are assigned to your business app. If not, your "
"credentials from step 1 may be wrong."
msgstr ""

#: ../channels/whatsapp/setup.rst:81
msgid "Welcome Message"
msgstr ""

#: ../channels/whatsapp/setup.rst:80
msgid ""
"Here you can define an optional text message which is automatically sent to "
"your customers when the initial message is received."
msgstr ""

#: ../channels/whatsapp/setup.rst:90
msgid "Automatic Reminders"
msgstr ""

#: ../channels/whatsapp/setup.rst:84
msgid ""
"Here you can control whether the automatic reminders about the customer "
"service window are sent to the customer when the window is about to expire."
msgstr ""

#: ../channels/whatsapp/setup.rst:87
msgid ""
"For more information on 24-hour customer service windows, take a look at "
"Meta's `conversation description <https://developers.facebook.com/docs/"
"whatsapp/pricing#customer-service-windows>`_ under \"Customer Service "
"Windows\"."
msgstr ""

#: ../channels/whatsapp/setup.rst:95
msgid "Reminder Message"
msgstr ""

#: ../channels/whatsapp/setup.rst:93
msgid ""
"If you want to use a custom reminder message before the 24-hour customer "
"service window closes, you can insert it here. Leave it empty to stay with "
"the default message."
msgstr ""

#: ../channels/whatsapp/setup.rst:99
msgid "Target Group"
msgstr ""

#: ../channels/whatsapp/setup.rst:98
msgid ""
"Here you can define the :doc:`group </manage/groups/index>` in which the "
"ticket should be created."
msgstr ""

#: ../channels/whatsapp/setup.rst:101
msgid ""
"After entering your data, click on **Submit**. After this step, the WhatsApp "
"channel is technically created. However, there is another important step to "
"take."
msgstr ""

#: ../channels/whatsapp/setup.rst:106
msgid "Step 3"
msgstr ""

#: ../channels/whatsapp/setup.rst:108
msgid ""
"This third step is about telling WhatsApp where they should send their data:"
msgstr ""

#: ../channels/whatsapp/setup.rst:110
msgid ""
"If you don't follow the instructions properly, your account shows up but you "
"aren't able to receive messages (because Meta/WhatsApp doesn't know where to "
"send them)!"
msgstr ""

#: ../channels/whatsapp/setup.rst:None
msgid "Step 3 of adding a WhatsApp account"
msgstr ""

#: ../channels/whatsapp/setup.rst:125
msgid "Callback URL"
msgstr ""

#: ../channels/whatsapp/setup.rst:120
msgid ""
"Click on the copy icon on the right side and head over to your WhatsApp "
"business app. Enter the copied URL in the corresponding field in your app. "
"You can find it in your `\"App Dashboard\" <https://developers.facebook.com/"
"apps/>`_ under \"WhatsApp > Configuration > Webhook > Callback URL\" (see "
"screenshot below). Paste it there."
msgstr ""

#: ../channels/whatsapp/setup.rst:138
msgid "Verify Token"
msgstr ""

#: ../channels/whatsapp/setup.rst:128
msgid "Copy this string too. Enter it directly below the pasted Callback URL."
msgstr ""

#: ../channels/whatsapp/setup.rst:0
msgid "Configuration section in WhatsApp app dashboard"
msgstr ""

#: ../channels/whatsapp/setup.rst:133
msgid ""
"After entering your data, click on **Verify and save** which triggers a "
"check if your system is accessible and configured correctly."
msgstr ""

#: ../channels/whatsapp/setup.rst:0
msgid "Webhook dialog"
msgstr ""

#: ../channels/whatsapp/setup.rst:156
msgid "Define webhook fields"
msgstr ""

#: ../channels/whatsapp/setup.rst:141
msgid ""
"Finally, go to the field below in the app dashboard and select \"Manage\" in "
"the \"Webhook fields\" section. This is needed that you'll get the message "
"as content:"
msgstr ""

#: ../channels/whatsapp/setup.rst:0
msgid "Select webhook fields in app dashboard"
msgstr ""

#: ../channels/whatsapp/setup.rst:148
msgid "Subscribe to \"messages\" by clicking in the checkbox:"
msgstr ""

#: ../channels/whatsapp/setup.rst:0
msgid "Select \"message\" as webhook field"
msgstr ""

#: ../channels/whatsapp/setup.rst:155
msgid ""
"You should now see the selected \"messages\" under the \"Webhook fields\" "
"caption as in the first screenshot."
msgstr ""

#: ../channels/whatsapp/setup.rst:158
msgid ""
"After finishing this step, you can click on the **Finish** button in Zammad "
"and you should now be ready to receive tickets from your WhatsApp channel!"
msgstr ""

#: ../index.rst:11
msgid "Manage"
msgstr ""

#: ../index.rst:37
msgid "Channels"
msgstr ""

#: ../index.rst:68
msgid "API (System-Documentation)"
msgstr ""

#: ../index.rst:68 ../misc/object-conditions/basics.rst:170
#: ../settings/system/index.rst:2
msgid "System"
msgstr ""

#: ../index.rst:88
msgid "Misc"
msgstr ""

#: ../index.rst:2
msgid "Zammad Admin Documentation"
msgstr ""

#: ../index.rst:5
msgid ""
"You are currently reading the Zammad administration documentation. There are "
"also :docs:`system </index.html>` and :user-docs:`user manuals </index."
"html>` available."
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/checklist.rst:2
msgid "Checklist"
msgstr ""

#: ../manage/checklist.rst:7
msgid ""
"The checklist feature allows agents to keep track of the tasks to be "
"completed. It is activated by default and shows up in another tab in the "
"right sidebar in the ticket view (see :user-docs:`here </extras/checklist."
"html>` what it looks like from agent's perspective)."
msgstr ""

#: ../manage/checklist.rst:None
msgid "Screenshot showing checklist feature in admin area."
msgstr ""

#: ../manage/checklist.rst:18
msgid ""
"To activate/deactivate the feature, simply switch the toggle labeled with "
"\"Enable Checklists\" at the top of the page."
msgstr ""

#: ../manage/checklist.rst:21
msgid ""
"You can optionally create one or more templates with predefined checklist "
"items. For this, just click on the \"New Checklist Template\" button and "
"define the checklist name and items. After submitting the form, the template "
"can be used in tickets."
msgstr ""

#: ../manage/checklist.rst:26
msgid ""
"You can clone or delete a template by clicking on the ︙ button and "
"selecting the corresponding action."
msgstr ""

#: ../manage/checklist.rst:29
msgid ""
"To edit the template, simply click on the name of the template. This opens a "
"dialog where you can edit the checklist and the items (add, rename, reorder, "
"delete them) and set the entire template to active/inactive."
msgstr ""

#: ../manage/checklist.rst:None
msgid "Screenshot showing the checklist template edit dialog."
msgstr ""

#: ../manage/checklist.rst:39
msgid "Remarks"
msgstr ""

#: ../manage/checklist.rst:41
msgid "It is only possible to add one checklist per ticket."
msgstr ""

#: ../manage/checklist.rst:42
msgid ""
"There is no specific permission for the checklist feature. You can turn it "
"off or on and provide optionally usable checklist templates."
msgstr ""

#: ../manage/checklist.rst:44
msgid ""
"If the agent has access to the ticket, they will also have access to its "
"checklist."
msgstr ""

#: ../manage/checklist.rst:46
msgid ""
"If an agent only has reading permissions for this ticket, the checklist will "
"be displayed in read-only mode."
msgstr ""

#: ../manage/checklist.rst:48
msgid "Customers have no access to the checklists at all and do not see them."
msgstr ""

#: ../manage/checklist.rst:49
msgid ""
"An agent can always overwrite and adjust the checklist, it can even be "
"deleted from the ticket. This applies also to checklists which are added in "
"a ticket based on a checklist template."
msgstr ""

#: ../manage/checklist.rst:52
msgid ""
"The checklist feature is currently a standalone feature. That means you "
"can't access the items or state of the checkboxes from other places in "
"Zammad like triggers or workflows."
msgstr ""

#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:172
msgid "Group Permissions"
msgstr ""

#: ../manage/groups/access-levels.rst:4
msgid ""
"When assigning an agent to a :doc:`group </manage/groups/index>`, 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 permission setting in the Edit User dialog"
msgstr ""

#: ../manage/groups/access-levels.rst:13
msgid "Use the group permission table to grant per-group privileges."
msgstr ""

#: ../manage/groups/access-levels.rst:15
msgid "Within each group, the different permissions 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 Permissions"
msgstr ""

#: ../manage/groups/access-levels.rst:31
msgid "There are two ways to define an agent's per-group permission levels:"
msgstr ""

#: ../manage/groups/access-levels.rst:33
msgid ""
"Directly, in the :ref:`Edit User dialog <user-details-group-access>` in the "
"table of group permissions:"
msgstr ""

#: ../manage/groups/access-levels.rst:0
msgid ""
"Screenshot showing the group assignment to a user in the user edit dialog."
msgstr ""

#: ../manage/groups/access-levels.rst:41
msgid "Simply set your permission levels right on the target user."
msgstr ""

#: ../manage/groups/access-levels.rst:43
msgid "Implicitly, by :ref:`editing a user role <role-settings-group-access>`"
msgstr ""

#: ../manage/groups/access-levels.rst:45
msgid ""
"First, head over to :doc:`Roles </manage/roles/index>` to set up the "
"permissions you want to assign. Example:"
msgstr ""

#: ../manage/groups/access-levels.rst:0
msgid "Group permissions table in edit role dialog"
msgstr ""

#: ../manage/groups/access-levels.rst:54
msgid ""
"Then you are good to go to assign the role to a user in the user edit "
"dialog. Example:"
msgstr ""

#: ../manage/groups/access-levels.rst:0
msgid "Screenshot shows the role assignment in the user edit dialog"
msgstr ""

#: ../manage/groups/access-levels.rst:63
msgid ""
"Make sure to click on the ➕ *Add* button after assigning the last group. "
"Otherwise, your last selection *will not* be saved."
msgstr ""

#: ../manage/groups/access-levels.rst:66
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:69
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 "
"permissions, create a role for them to share—that's what roles are for!"
msgstr ""

#: ../manage/groups/access-levels.rst:74
msgid "🤔 **Can't see the group permission table?**"
msgstr ""

#: ../manage/groups/access-levels.rst:76
msgid ""
"Please make sure that you have selected the ``ticket.agent`` permission for "
"the user or role."
msgstr ""

#: ../manage/groups/access-levels.rst:80
msgid "Examples"
msgstr ""

#: ../manage/groups/access-levels.rst:90
msgid "“The Standard Issue”"
msgstr ""

#: ../manage/groups/access-levels.rst:0
msgid "The group permission table, checked \"Full\""
msgstr ""

#: ../manage/groups/access-levels.rst:88
msgid ""
"When a system only has one group, this is the default permission level "
"assigned to all agents. Unless you have special needs in mind, this is the "
"way to go."
msgstr ""

#: ../manage/groups/access-levels.rst:100
msgid "“The Supervisor”"
msgstr ""

#: ../manage/groups/access-levels.rst:0
msgid ""
"The group permission table, checked \"Read\", \"Create\", \"Change\", and "
"\"Overview"
msgstr ""

#: ../manage/groups/access-levels.rst:98
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:110
msgid "“The Meddler”"
msgstr ""

#: ../manage/groups/access-levels.rst:0
msgid ""
"The group permission table, checked \"Read\", \"Change\", and \"Overview"
msgstr ""

#: ../manage/groups/access-levels.rst:108
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:119
msgid "“The Intern”"
msgstr ""

#: ../manage/groups/access-levels.rst:0
msgid "The group permission table, checked \"Create\""
msgstr ""

#: ../manage/groups/access-levels.rst:118
msgid ""
"Agents with only “create” permission 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:30 ../manage/macros.rst:36
#: ../manage/slas/index.rst:94 ../manage/trigger.rst:28
#: ../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
msgid "Groups"
msgstr ""

#: ../manage/groups/index.rst:4
msgid ""
"This is the group management area. 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."
msgstr ""

#: ../manage/groups/index.rst:19
msgid ""
"For example, you might want set up a group *Management* for confidential "
"tickets. With access levels, you can configure that only a few selected "
"agents will have access to these tickets."
msgstr ""

#: ../manage/groups/index.rst:23
msgid ""
"For an additional way to categorize tickets, have a look at :doc:`/manage/"
"tags`."
msgstr ""

#: ../manage/groups/index.rst:27
msgid ""
"Zammad users are global to the whole instance. Restriction to specific "
"groups is not possible."
msgstr ""

#: ../manage/groups/index.rst:37
msgid "If the *Group* field does not appear in the ticket view, ensure that:"
msgstr ""

#: ../manage/groups/index.rst:39
msgid "you have created more than one group"
msgstr ""

#: ../manage/groups/index.rst:40
msgid "the current user has \"change\" permissions to more than one group"
msgstr ""

#: ../manage/groups/index.rst:42
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:12
msgid "Please note that groups cannot be removed."
msgstr ""

#: ../manage/groups/settings.rst:15
msgid ""
"This is the name your agents (and customers when using :doc:`/channels/web`) "
"will see within the Zammad-UI."
msgstr ""

#: ../manage/groups/settings.rst:34
msgid "Parent group"
msgstr ""

#: ../manage/groups/settings.rst:19
msgid ""
"You can define *another* group as a parent group here. This is useful if you "
"want to create group hierarchies. In such a hierarchy (child/parent "
"relation), the tree of the parent group is inherited to the child group. "
"That means if you move a group which itself has child groups, the child "
"groups are \"moved\" accordingly. However, there is no inheritance of "
"membership or permissions. That means you can treat each group as an "
"individual group - even if they have a child/parent relation."
msgstr ""

#: ../manage/groups/settings.rst:27
msgid ""
"Zammad doesn't show you any child group of the currently selected group. "
"This would lead to a circular reference!"
msgstr ""

#: ../manage/groups/settings.rst:30
msgid ""
"Zammad supports 10 levels of hierarchy for groups on PostgreSQL systems. If "
"you are using a MySQL database, it is limited to 6 levels. In case you are "
"using MySQL, you should consider to migrate your database anyway (see :docs:"
"`here </appendix/migrate-to-postgresql.html>` for more information). MySQL "
"will be deprecated with Zammad 7."
msgstr ""

#: ../manage/groups/settings.rst:39
msgid "Assignment timeout"
msgstr ""

#: ../manage/groups/settings.rst:37
msgid ""
"The time in minutes after which the ticket's ownership will revert back to "
"*unassigned* after the assigned agent hasn't worked on the ticket. This "
"timeout does *not* take any working hours in account."
msgstr ""

#: ../manage/groups/settings.rst:59
msgid "Follow-up possible"
msgstr ""

#: ../manage/groups/settings.rst:42
msgid ""
"This option allows you to decide how Zammad should react if a customer "
"replies to a closed ticket (no matter if by e.g. email or UI)."
msgstr ""

#: ../manage/groups/settings.rst:46 ../manage/groups/settings.rst:67
#: ../misc/object-conditions/basics.rst:122
#: ../misc/object-conditions/basics.rst:137
msgid "yes"
msgstr ""

#: ../manage/groups/settings.rst:46
msgid "The ticket will be reopened. This is the default value."
msgstr ""

#: ../manage/groups/settings.rst:50
msgid "do not reopen Ticket but create new Ticket"
msgstr ""

#: ../manage/groups/settings.rst:49
msgid ""
"The ticket will remain closed and Zammad will create a new ticket instead. "
"The new ticket contains the customers reply only."
msgstr ""

#: ../manage/groups/settings.rst:59
msgid "do not reopen ticket after certain time but create new ticket"
msgstr ""

#: ../manage/groups/settings.rst:53
msgid ""
"The ticket can be reopened unless the specified number of days *after last "
"ticket closure* has been exceeded. If the time limit is exceeded, Zammad "
"will create a new ticket instead of reopening."
msgstr ""

#: ../manage/groups/settings.rst:57
msgid ""
"Choosing this option will provide the option *Reopening time in days* which "
"requires you to provide the number of days you want Zammad to wait until it "
"creates new tickets."
msgstr ""

#: ../manage/groups/settings.rst:70
msgid "Assign follow-ups"
msgstr ""

#: ../manage/groups/settings.rst:62
msgid ""
"This setting allows you to decide if, upon a reopen of a ticket, the last "
"assigned owner should stay assigned or if Zammad should reset the owner to "
"nobody."
msgstr ""

#: ../manage/groups/settings.rst:67
msgid ""
"The ticket will remain with the last agent who owned it. This is the default "
"value."
msgstr ""

#: ../manage/groups/settings.rst:70 ../misc/object-conditions/basics.rst:123
#: ../misc/object-conditions/basics.rst:138
msgid "no"
msgstr ""

#: ../manage/groups/settings.rst:70
msgid "The owner assignment of the ticket will be removed."
msgstr ""

#: ../manage/groups/settings.rst:85
msgid "Sending Email Address"
msgstr ""

#: ../manage/groups/settings.rst:73
msgid ""
"Select which sender's email address Zammad will use outbound for replying on "
"a ticket in this group."
msgstr ""

#: ../manage/groups/settings.rst:76
msgid "**You don't have an email address configured yet?**"
msgstr ""

#: ../manage/groups/settings.rst:78
msgid "Please configure an email based channel before here"
msgstr ""

#: ../manage/groups/settings.rst:80
msgid ":doc:`Channels → Email </channels/email/index>`"
msgstr ""

#: ../manage/groups/settings.rst:81
msgid ":doc:`Channels → Microsoft 365 IMAP </channels/microsoft365/index>`"
msgstr ""

#: ../manage/groups/settings.rst:82
msgid ""
":doc:`Channels → Microsoft 365 Graph </channels/microsoft365-graph/index>`"
msgstr ""

#: ../manage/groups/settings.rst:83
msgid ":doc:`Channels → Google </channels/google/index>`"
msgstr ""

#: ../manage/groups/settings.rst:85
msgid "and come back afterwards."
msgstr ""

#: ../manage/groups/settings.rst:90
msgid "Signature"
msgstr ""

#: ../manage/groups/settings.rst:88
msgid ""
"Choose which :doc:`signature </channels/email/signatures>` to use when "
"replying to tickets in this group. Leaving this option unset will send "
"emails without any signature."
msgstr ""

#: ../manage/groups/settings.rst:98
msgid "Shared Drafts"
msgstr ""

#: ../manage/groups/settings.rst:93
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:97
msgid ""
"Learn more about shared drafts :user-docs:`in our user documentation </"
"extras/shared-drafts.html>`."
msgstr ""

#: ../manage/groups/settings.rst:101
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:105
msgid ""
"Don't need the group anymore? If you can't or don't want to recycle (rename) "
"the group, you can also set it to inactive. Agents will no longer be able to "
"see or edit tickets in this group. However, customers can still interact "
"with their existing tickets in an inactive group."
msgstr ""

#: ../manage/groups/settings.rst:112
msgid ""
"Want to handle tickets from an inactive group, which are updated by "
"customers?"
msgstr ""

#: ../manage/groups/settings.rst:115
msgid ""
"You could e.g. create a trigger which moves them to another group when they "
"got updated. Create this trigger before deactivating the group so it is "
"selectable in the trigger configuration."
msgstr ""

#: ../manage/groups/settings.rst:121
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:130
msgid "Screenshot showing how a group configuration can look like."
msgstr ""

#: ../manage/groups/settings.rst:130
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 processes and more with "
"the **knowledge base**."
msgstr ""

#: ../manage/knowledge-base.rst:7
msgid ""
"This document describes how to **configure** the knowledge base. For details "
"on how to **use and edit** it, please refer to the :user-docs:`Zammad User "
"Documentation </extras/knowledge-base.html>`."
msgstr ""

#: ../manage/knowledge-base.rst:15
msgid "Sample Knowledge Base Index"
msgstr ""

#: ../manage/knowledge-base.rst:15
msgid "See a live demo at https://support.zammad.com/help."
msgstr ""

#: ../manage/knowledge-base.rst:17
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:21
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:25
msgid "Features"
msgstr ""

#: ../manage/knowledge-base.rst:27
msgid "🌍 Multi-language support"
msgstr ""

#: ../manage/knowledge-base.rst:28
msgid "🙈 Visibility settings (**draft**, **staff-only**, or **public**)"
msgstr ""

#: ../manage/knowledge-base.rst:29
msgid "🔍 Full text search"
msgstr ""

#: ../manage/knowledge-base.rst:30
msgid "📅 Scheduled publishing"
msgstr ""

#: ../manage/knowledge-base.rst:31
msgid "📎 File attachments"
msgstr ""

#: ../manage/knowledge-base.rst:32
msgid ""
"🔗 Wiki-style internal linking to both 💡 **KB answers** and 📋 **tickets**"
msgstr ""

#: ../manage/knowledge-base.rst:33
msgid "🖼️ Rich text editor + embedded images"
msgstr ""

#: ../manage/knowledge-base.rst:38
msgid ""
"To enable the knowledge base, first select the languages/locales you wish to "
"publish in:"
msgstr ""

#: ../manage/knowledge-base.rst:45
msgid "Knowledge Base: Initial setup"
msgstr ""

#: ../manage/knowledge-base.rst:45
msgid ""
"You must choose at least one. (Don't worry, you can always change them "
"later!)"
msgstr ""

#: ../manage/knowledge-base.rst:48
msgid ""
"Read on for details about each section of the knowledge base configuration."
msgstr ""

#: ../manage/knowledge-base.rst:51
msgid "Theme"
msgstr ""

#: ../manage/knowledge-base.rst:57
msgid "Knowledge Base: Configure theme"
msgstr ""

#: ../manage/knowledge-base.rst:57
msgid "Customize the appearance of the knowledge base."
msgstr ""

#: ../manage/knowledge-base.rst:0
msgid "Icon & Link Color"
msgstr ""

#: ../manage/knowledge-base.rst:60
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:64
msgid "Applies to the area surrounding the search bar."
msgstr ""

#: ../manage/knowledge-base.rst:0
msgid "Header Link Color"
msgstr ""

#: ../manage/knowledge-base.rst:67
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:71
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:75
msgid "a general RSS feed of the whole knowledge base (top level)"
msgstr ""

#: ../manage/knowledge-base.rst:76
msgid ""
"a category specific RSS feed of the category you're in (also applies to "
"answers you're viewing)"
msgstr ""

#: ../manage/knowledge-base.rst:79
msgid "This setting by default is set to ``no``."
msgstr ""

#: ../manage/knowledge-base.rst:83
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:88
msgid ""
"Defines the selection of icons that may be used when creating/editing "
"categories."
msgstr ""

#: ../manage/knowledge-base.rst:91
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:98
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:103
msgid "Languages"
msgstr ""

#: ../manage/knowledge-base.rst:109
msgid "Knowledge Base: Configure languages"
msgstr ""

#: ../manage/knowledge-base.rst:109
msgid "Add or remove locales, or reassign the default."
msgstr ""

#: ../manage/knowledge-base.rst:111
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:115
msgid ""
"The default locale is displayed when the visitor's locale is not supported."
msgstr ""

#: ../manage/knowledge-base.rst:117
msgid ""
"Articles that have not yet been translated into a given language will be "
"hidden from that locale."
msgstr ""

#: ../manage/knowledge-base.rst:121
msgid "Public Menu"
msgstr ""

#: ../manage/knowledge-base.rst:123
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:130
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:133
msgid "You can adjust every URL on language level."
msgstr ""

#: ../manage/knowledge-base.rst:139
msgid "Knowledge Base: Configure public menu"
msgstr ""

#: ../manage/knowledge-base.rst:139
msgid ""
"🧭 Customize the nav menu that appears in the header of the knowledge base."
msgstr ""

#: ../manage/knowledge-base.rst:168
msgid "Arranging URLs"
msgstr ""

#: ../manage/knowledge-base.rst:142
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:146 ../manage/public-links.rst:39
#: ../manage/time-accounting.rst:151 ../manage/time-accounting.rst:165
#: ../system/maintenance.rst:31
msgid "Title"
msgstr ""

#: ../manage/knowledge-base.rst:146
msgid "This is the URL title that's being displayed to your users."
msgstr ""

#: ../manage/knowledge-base.rst:149 ../manage/webhook/log.rst:14
#: ../system/integrations/elasticsearch.rst:57
msgid "URL"
msgstr ""

#: ../manage/knowledge-base.rst:149
msgid "The actual URL the user is going to open upon clicking."
msgstr ""

#: ../manage/knowledge-base.rst:153
msgid "Target"
msgstr ""

#: ../manage/knowledge-base.rst:152
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:156
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:168
msgid "Change URLs position"
msgstr ""

#: ../manage/knowledge-base.rst:160
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:167
msgid ""
"Re-arranging URL positions works for the header menu just as the footer menu"
msgstr ""

#: ../manage/knowledge-base.rst:171
msgid "Custom URL"
msgstr ""

#: ../manage/knowledge-base.rst:173
msgid "This feature is only available on **self-hosted** instances."
msgstr ""

#: ../manage/knowledge-base.rst:179
msgid "Knowledge Base: Configure custom URL"
msgstr ""

#: ../manage/knowledge-base.rst:179
msgid "Relocate the knowledge base to the URL of your choosing."
msgstr ""

#: ../manage/knowledge-base.rst:181
msgid ""
"By default, the knowledge base will appear at the same domain as your Zammad "
"instance, under ``/help``."
msgstr ""

#: ../manage/knowledge-base.rst:184
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:195
msgid "Knowledge Base: Delete knowledge base"
msgstr ""

#: ../manage/knowledge-base.rst:195
msgid "Permanently delete the knowledge base and all the articles within it."
msgstr ""

#: ../manage/knowledge-base.rst:197
msgid ""
"Use this panel to delete the knowledge base. If you wish to unpublish it "
"without deleting all of its content, simply disable it via the toggle button "
"at the top of the window instead."
msgstr ""

#: ../manage/knowledge-base.rst:202
msgid "Permissions"
msgstr ""

#: ../manage/knowledge-base.rst:204
msgid ""
"The general access to the knowledge base is managed via ``knowledge_base."
"reader`` and ``knowledge_base.editor`` permissions. You can find more "
"information about roles and permissions :doc:`here <roles/index>`."
msgstr ""

#: ../manage/knowledge-base.rst:209
msgid ""
"If you want to grant more granular permissions than the global read/edit "
"permissions (e.g. edit permissions only for specific parts of the knowledge "
"base), you can do so by following the steps below:"
msgstr ""

#: ../manage/knowledge-base.rst:213
msgid ""
"First create the base structure of the knowledge base (if not already done)"
msgstr ""

#: ../manage/knowledge-base.rst:214
msgid ""
"Create or choose one or more roles which should have granular permissions"
msgstr ""

#: ../manage/knowledge-base.rst:215
msgid "Grant the ``knowledge_base.reader`` permission to the desired role(s)"
msgstr ""

#: ../manage/knowledge-base.rst:216
msgid "Edit the permissions of each (sub-)category of the knowledge base"
msgstr ""

#: ../manage/knowledge-base.rst:217
msgid ""
"Assign the role to one or more users who should be able to edit the "
"knowledge base (partially)"
msgstr ""

#: ../manage/knowledge-base.rst:222
msgid "The permissions of a parent category are inherited to sub-categories."
msgstr ""

#: ../manage/knowledge-base.rst:223
msgid ""
"The permission ``knowledge_base.reader`` can be widened or restricted in sub-"
"categories."
msgstr ""

#: ../manage/knowledge-base.rst:225
msgid ""
"The permission ``knowledge_base.editor`` **can't** be adjusted in sub-"
"categories."
msgstr ""

#: ../manage/knowledge-base.rst:227
msgid ""
"Have a look at the :user-docs:`knowledge base section </extras/knowledge-"
"base.html>` in the user documentation where you can find more information "
"about the usage."
msgstr ""

#: ../manage/macros.rst:2
msgid "Macros"
msgstr ""

#: ../manage/macros.rst:4
msgid "Macros are **🖱️ one-click actions** 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
msgid "How Do Macros 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:11
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:73
msgid "Actions"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:19
msgid "You can create actions to:"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:21
msgid "set ticket attributes (priority, state, group, etc.)"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:22
msgid "add new notes to a ticket"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:24
msgid "There are **no** actions for:"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:26
msgid "sending a reply to the customer"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:28
msgid ""
"Unlike triggers, the scheduler, and text modules, macro actions do **not** "
"support the use of :doc:`/misc/variables`."
msgstr ""

#: ../manage/macros/how-do-they-work.rst:32
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:37
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:42
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:46
msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:49
msgid "Choose \"inactive\" to disable this macro without deleting it."
msgstr ""

#: ../manage/macros/how-do-they-work.rst:52
msgid "Managing Macros"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:54
msgid ""
"Edit your macros by simply clicking on it. You can delete or even clone "
"existing macros by clicking on the ︙ action menu and select the desired "
"action:"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:None
msgid "Screenshot showing the macro action menu"
msgstr ""

#: ../manage/macros/how-do-they-work.rst:62
msgid ""
"When cloning a macro, make sure to click \"Submit\" for the duplicate to be "
"created."
msgstr ""

#: ../manage/macros/learn-by-example.rst:2
msgid "Macro 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:7
msgid ""
"To learn about macros in detail, go to the section :doc:`/manage/macros/how-"
"do-they-work`."
msgstr ""

#: ../manage/macros/learn-by-example.rst:10
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:0
#: ../misc/object-conditions/basics.rst:173
msgid "State"
msgstr ""

#: ../manage/macros/learn-by-example.rst:13
msgid "closed"
msgstr ""

#: ../manage/macros/learn-by-example.rst:0 ../manage/tags.rst:2
#: ../misc/object-conditions/basics.rst:191
msgid "Tags"
msgstr ""

#: ../manage/macros/learn-by-example.rst:14
msgid "add ``spam``"
msgstr ""

#: ../manage/macros/learn-by-example.rst:0
#: ../misc/object-conditions/basics.rst:157
msgid "Owner"
msgstr ""

#: ../manage/macros/learn-by-example.rst:15
#: ../manage/macros/learn-by-example.rst:33
#: ../misc/object-conditions/basics.rst:96
#: ../misc/object-conditions/basics.rst:162
#: ../misc/object-conditions/basics.rst:188
msgid "current user"
msgstr ""

#: ../manage/macros/learn-by-example.rst:0
msgid "Screenshot showing spam macro configuration"
msgstr ""

#: ../manage/macros/learn-by-example.rst:22
msgid ""
"💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up "
"unwanted tickets."
msgstr ""

#: ../manage/macros/learn-by-example.rst:25
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:30
msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)"
msgstr ""

#: ../manage/macros/learn-by-example.rst:31
msgid "pending reminder"
msgstr ""

#: ../manage/macros/learn-by-example.rst:0
msgid "Pending Till"
msgstr ""

#: ../manage/macros/learn-by-example.rst:32
msgid "relative / 7 / days"
msgstr ""

#: ../manage/macros/learn-by-example.rst:0
msgid "Screenshot showing postpone macro configuration"
msgstr ""

#: ../manage/organizations/index.rst:20
msgid "via the Admin Panel"
msgstr ""

#: ../manage/organizations/index.rst:20
msgid "via CSV import"
msgstr ""

#: ../manage/organizations/index.rst:20
msgid "via REST API (system documentation)"
msgstr ""

#: ../manage/organizations/index.rst:2
msgid "Organizations"
msgstr ""

#: ../manage/organizations/index.rst:4
msgid ""
"Organizations can be managed individually via UI, via CSV import or the API."
msgstr ""

#: ../manage/organizations/index.rst:6
msgid ""
"Organizations can be managed by admins. However, in most cases agents can, "
"too (using the :user-docs:`ticket pane </extras/organizations.html>` or "
"organization detail page)."
msgstr ""

#: ../manage/organizations/index.rst:15 ../manage/users/index.rst:16
msgid "Creating and editing users directly in the Admin Panel"
msgstr ""

#: ../manage/organizations/index.rst:15
msgid ""
"The simplest way to manage organizations is directly in the organization "
"detail view."
msgstr ""

#: ../manage/organizations/index.rst:18
msgid "Learn more about managing organizations..."
msgstr ""

#: ../manage/organizations/index.rst:27
msgid "**There are some technical limitations:**"
msgstr ""

#: ../manage/organizations/index.rst:29
msgid ""
"Organizations currently cannot be removed. The only exception is Zammad's :"
"doc:`/system/data-privacy` function."
msgstr ""

#: ../manage/organizations/index.rst:31
msgid ""
"Unlike users, agents cannot just create new organizations. Check the :doc:"
"`permission reference </manage/roles/admin-permissions>` to learn more."
msgstr ""

#: ../manage/organizations/index.rst:34
msgid ""
"Because of how organization references work with users, external syncs like "
"LDAP or Exchange *do not* support organization mapping. If this is relevant "
"to you, consider domain based assignments."
msgstr ""

#: ../manage/organizations/index.rst:37
msgid ""
"BIG organizations can cause *performance issues*. Especially organizations "
"with many members can cause a fairly high system load if their members run "
"many updates, for example ticket creations or frequent communication."
msgstr ""

#: ../manage/organizations/index.rst:44
msgid "Reference Guide: Organization Details"
msgstr ""

#: ../manage/organizations/index.rst:46
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:54
msgid ""
"The edit organization dialog, showing the various organization detail fields"
msgstr ""

#: ../manage/organizations/index.rst:54
msgid "User details can be set in the **New/Edit Organization** dialog."
msgstr ""

#: ../manage/organizations/index.rst:82
msgid "📢 Shared Organization"
msgstr ""

#: ../manage/organizations/index.rst:57
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:63
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:67
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:71
msgid "The default value on creation dialogues is ``yes``."
msgstr ""

#: ../manage/organizations/index.rst:73
msgid ""
"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:82
msgid ""
"Members of shared organization have access to organization based overviews"
msgstr ""

#: ../manage/organizations/index.rst:90
msgid "🗄️ Domain based assignment"
msgstr ""

#: ../manage/organizations/index.rst:85
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:90
msgid "The default value on creation dialogues is ``no``"
msgstr ""

#: ../manage/organizations/index.rst:99
msgid "🌐 Domain"
msgstr ""

#: ../manage/organizations/index.rst:93
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:97
msgid ""
"Currently, 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:112 ../manage/users/index.rst:113
msgid "👑 VIP"
msgstr ""

#: ../manage/organizations/index.rst:102
msgid ""
"This flag is a way for your team to indicate high-status organizations. Just "
"as with customers, 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/organizations/index.rst:0
msgid "Ticket view showing a VIP organization's avatar with a crown on it"
msgstr ""

#: ../manage/organizations/index.rst:112
msgid "VIP organizations are displayed with a crown above their avatars."
msgstr ""

#: ../manage/organizations/index.rst:122 ../manage/users/index.rst:123
msgid "📑 Note"
msgstr ""

#: ../manage/organizations/index.rst:115 ../manage/users/index.rst:116
msgid "Notes are visible to all staff members, **including agents**."
msgstr ""

#: ../manage/organizations/index.rst:117
msgid ""
"😵 **Are you using the Note field to keep track of your own \"custom\" "
"organization attributes?**"
msgstr ""

#: ../manage/organizations/index.rst:120
msgid "Wish you could add your own fields to organizations?"
msgstr ""

#: ../manage/organizations/index.rst:122 ../manage/users/index.rst:123
msgid "You can! To learn more, see :doc:`/system/objects`."
msgstr ""

#: ../manage/organizations/index.rst:137 ../manage/users/index.rst:148
msgid "▶️ Active"
msgstr ""

#: ../manage/organizations/index.rst:125
msgid ""
"Disabling this flag is a soft alternative to deleting an organization. So "
"what's the difference?"
msgstr ""

#: ../manage/organizations/index.rst:128
msgid ""
"There is no way to restore a deleted organization; inactive organizations "
"can be reactivated at any time."
msgstr ""

#: ../manage/organizations/index.rst:131
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:137
msgid ""
"A slashed-out 🏢 icon indicates an inactive organization. In other cases, "
"inactive organizations are grayed 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:17
msgid "The CSV import dialog"
msgstr ""

#: ../manage/organizations/via-csv-import.rst:12
#: ../manage/users/via-csv-import.rst:17
msgid "Use the **Import** button to open the CSV import dialog."
msgstr ""

#: ../manage/organizations/via-csv-import.rst:15
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:29
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:31
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:33
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:36
msgid "For instance:"
msgstr ""

#: ../manage/organizations/via-csv-import.rst:40
msgid ""
"Several *organization members* can be added. Separate multiple values for "
"one field with ``~~~`` as above."
msgstr ""

#: ../manage/organizations/via-csv-import.rst:44
#: ../manage/users/via-csv-import.rst:48
msgid "Step 3: Import Your .csv to Zammad"
msgstr ""

#: ../manage/organizations/via-csv-import.rst:46
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:54
#: ../manage/users/via-csv-import.rst:58
msgid "CSV import test run and confirmation dialog"
msgstr ""

#: ../manage/organizations/via-csv-import.rst:54
#: ../manage/users/via-csv-import.rst:58
msgid "CSV import always begins with a preview / test run."
msgstr ""

#: ../manage/organizations/via-csv-import.rst:56
#: ../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:58
msgid ""
"Records are updated when the imported data contains a ``name`` that matches "
"an existing organization entry."
msgstr ""

#: ../manage/organizations/via-csv-import.rst:61
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:64
#: ../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. See :ref:`organization-details-reference` for help with the New/"
"Edit Organization dialog."
msgstr ""

#: ../manage/organizations/via-the-admin-panel.rst:11
msgid "👥 Creating and editing organizations"
msgstr ""

#: ../manage/organizations/via-the-admin-panel.rst:9
msgid ""
"Click the **New Organization** button to create a new one. Simply click on "
"an existing organization to edit it. You can even clone an organization by "
"using the icon in the \"Action\" column."
msgstr ""

#: ../manage/organizations/via-the-admin-panel.rst:32
msgid "🗑️ Deleting organizations"
msgstr ""

#: ../manage/organizations/via-the-admin-panel.rst:14
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:23
#: ../manage/users/via-the-admin-panel.rst:20
msgid "Use the ⋮ **Actions** menu to open the **Delete User** dialog."
msgstr ""

#: ../manage/organizations/via-the-admin-panel.rst:25
#: ../manage/users/via-the-admin-panel.rst:22
msgid "💥 **Deleting a customer destroys all their associated tickets!**"
msgstr ""

#: ../manage/organizations/via-the-admin-panel.rst:27
#: ../manage/users/via-the-admin-panel.rst:24
msgid "To learn more, see :doc:`/system/data-privacy`."
msgstr ""

#: ../manage/organizations/via-the-admin-panel.rst:31
msgid ""
"Technically organization removal is possible via :docs:`Zammad's API </api/"
"organization.html>`, 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 on. You can "
"add new overviews, edit or delete them. They can be used for individual "
"agents or agent groups. Overviews only show tickets for which the user has "
"permissions (group or role based)."
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 should use a maximum of 15-20 overviews. Please note that any overview "
"will only show a maximum of 2100 elements."
msgstr ""

#: ../manage/overviews.rst:20
msgid ""
"The following attributes can be set when creating or editing overviews. Have "
"a look under the screenshot where you can find an explanation for each field."
msgstr ""

#: ../manage/overviews.rst:35
msgid ""
"Available for the following roles / Restrict to only the following users"
msgstr ""

#: ../manage/overviews.rst:28
msgid ""
"Define :doc:`roles <roles/index>` that are supposed to see and use the "
"overview in question."
msgstr ""

#: ../manage/overviews.rst:31
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:35
msgid "The setting \"available for the following roles\" is mandatory."
msgstr ""

#: ../manage/overviews.rst:47
msgid "Only available for users with shared organization"
msgstr ""

#: ../manage/overviews.rst:38
msgid ""
"This is important if the available role is a customer. Whether you select "
"\"Yes\" or \"No\" depends on whether you want one of your customer's "
"contacts to see all of their organization's tickets."
msgstr ""

#: ../manage/overviews.rst:44
msgid ""
"Shared organization is a setting in the organization management. See :doc:`/"
"manage/organizations/index` for more information."
msgstr ""

#: ../manage/overviews.rst:47
msgid "\"Users\" also refers to the customer role in this case."
msgstr ""

#: ../manage/overviews.rst:61
msgid "Only available for users which are absence replacements for other users"
msgstr ""

#: ../manage/overviews.rst:50
msgid ""
"This selection refers to the setting in the user preferences (profile-"
"picture / initials of agent in the left corner > profile > out of office). "
"If this option is checked, this overview is only displayed for users who "
"have been set as a substitution. See \"Out of office function\" in the :user-"
"docs:`user documentation </extras/profile-and-settings.html>` for more "
"details."
msgstr ""

#: ../manage/overviews.rst:58
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:71
msgid "Conditions for shown tickets"
msgstr ""

#: ../manage/overviews.rst:66
msgid ""
"Which tickets should be shown in this overview? The conditions can be seen "
"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 avoid duplicate content."
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:91
msgid "Attributes"
msgstr ""

#: ../manage/overviews.rst:76
msgid "Which attributes (column headers) shall be shown in the overview?"
msgstr ""

#: ../manage/overviews.rst:78
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:85
msgid ""
"These settings can also be adjusted individually by admins at a later time "
"(in the overview, top right: Options)."
msgstr ""

#: ../manage/overviews.rst:90
msgid ""
"Please note that overview column and sort settings are global settings which "
"affect all users seeing those overviews."
msgstr ""

#: ../manage/overviews.rst:119
msgid "Sorting, Grouping and Active"
msgstr ""

#: ../manage/overviews.rst:0
msgid "Sorting by"
msgstr ""

#: ../manage/overviews.rst:97
msgid ""
"In which order should the tickets be displayed? Choose the attribute you "
"want to sort by."
msgstr ""

#: ../manage/overviews.rst:0
msgid "Sorting order"
msgstr ""

#: ../manage/overviews.rst:101
msgid "The direction of the sorting (ascending or descending)."
msgstr ""

#: ../manage/overviews.rst:0
msgid "Grouping by"
msgstr ""

#: ../manage/overviews.rst:104
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:107
msgid "The direction of the grouping."
msgstr ""

#: ../manage/overviews.rst:110
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:116
msgid ""
"Users can define their own overview order. Renaming or reordering overviews "
"has no effect on custom orders!"
msgstr ""

#: ../manage/overviews.rst:119
msgid ""
"You can learn more about this setting :user-docs:`in the user documentation "
"</extras/profile-and-settings.html#user-profile-settings>`."
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:16
msgid "Adding New Public Links"
msgstr ""

#: ../manage/public-links.rst:18
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:34
msgid "Link"
msgstr ""

#: ../manage/public-links.rst:22
msgid ""
"This is the actual target page you're linking to. Zammad only allows URLs "
"that start with either ``http://`` or ``https://``."
msgstr ""

#: ../manage/public-links.rst:27
msgid ""
"Do not use data privacy and terms of service URLs of ``zammad.com`` or "
"``zammad.org``."
msgstr ""

#: ../manage/public-links.rst:30
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:34
msgid "This function was made to allow you to link to your *own resources*."
msgstr ""

#: ../manage/public-links.rst:37
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:42
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:46
msgid "Use this to describe the link. This value is *optional*."
msgstr ""

#: ../manage/public-links.rst:83 ../misc/object-conditions/basics.rst:63
#: ../system/core-workflows/how-do-they-work.rst:23
msgid "Context"
msgstr ""

#: ../manage/public-links.rst:50
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:54
msgid "You can currently select from:"
msgstr ""

#: ../manage/public-links.rst:56 ../manage/public-links.rst:72
msgid "Forgot Password Screen"
msgstr ""

#: ../manage/public-links.rst:57 ../manage/public-links.rst:65
msgid "Login Screen"
msgstr ""

#: ../manage/public-links.rst:58 ../manage/public-links.rst:79
msgid "Signup Screen"
msgstr ""

#: ../manage/public-links.rst:60
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:90
msgid "Display in new tab"
msgstr ""

#: ../manage/public-links.rst:86
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:95
msgid "Manage Existing Public Links"
msgstr ""

#: ../manage/public-links.rst:100
msgid "Re-arrange Links"
msgstr ""

#: ../manage/public-links.rst:102
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 by using "
"the ≣ handle."
msgstr ""

#: ../manage/public-links.rst:107
msgid "These changes are affective immediately."
msgstr ""

#: ../manage/public-links.rst:112
msgid "Actions for Existing Links"
msgstr ""

#: ../manage/public-links.rst:119
msgid "Updating existing entries"
msgstr ""

#: ../manage/public-links.rst:115
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:119
msgid "You'll be given the same options as you have during the link creation."
msgstr ""

#: ../manage/public-links.rst:133
msgid "Cloning & Removing"
msgstr ""

#: ../manage/public-links.rst:122
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:125
msgid ""
"Zammad will open a new public link dialogue with the existing settings "
"filled in."
msgstr ""

#: ../manage/public-links.rst:128
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. Be aware that the deletion is **final**. There's no way "
"to bring back removed public links."
msgstr ""

#: ../manage/public-links.rst:0
msgid "Screenshot showing the ⋮ action menu in public links"
msgstr ""

#: ../manage/report-profiles.rst:2
msgid "Report Profiles and Reporting"
msgstr ""

#: ../manage/report-profiles.rst:7
msgid ""
"The reporting is useful to view statistics, get an overview of the number of "
"tickets (e.g. tickets of a specific customer) and to download ticket data "
"from Zammad. In the following section you will find an instruction on how to "
"create and change report profiles. In a separate section you can find "
"information on basic usage of the reporting UI itself. If the reporting "
"options in Zammad are not enough for you, we added a section about external "
"reporting tools you can use."
msgstr ""

#: ../manage/report-profiles.rst:15
msgid ""
"To create and edit report profiles, ``admin.report_profile`` permission is "
"required. To use the reporting itself, ``report`` permission is required."
msgstr ""

#: ../manage/report-profiles.rst:18
msgid ""
"⚠️ Be aware that granting users the ``reporting`` permission may leak "
"information. On the one hand, users could see ticket metadata that they do "
"not actually have access to. On the other hand, a possibly large scale of "
"ticket information can easily be downloaded as a spreadsheet."
msgstr ""

#: ../manage/report-profiles.rst:24
msgid "Create and Edit Profiles"
msgstr ""

#: ../manage/report-profiles.rst:26
msgid ""
"Report profiles are used to 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. You can filter the tickets as in other places "
"in Zammad based on different conditions."
msgstr ""

#: ../manage/report-profiles.rst:34
msgid "The edit dialog looks like this:"
msgstr ""

#: ../manage/report-profiles.rst:None
msgid "Screenshot shows creation of report profile"
msgstr ""

#: ../manage/report-profiles.rst:39
msgid ""
"This example shows the statistics of all tickets of the organization "
"\"Awesome Customer Inc.\" that were created in the last month."
msgstr ""

#: ../manage/report-profiles.rst:42
msgid ""
"All configured report profiles are displayed in the reporting area and you "
"can switch between them with one click. Have a look at the next section to "
"learn some basics about the usage of the reporting."
msgstr ""

#: ../manage/report-profiles.rst:47
msgid "Using the Reporting"
msgstr ""

#: ../manage/report-profiles.rst:49
msgid ""
"You can find the reporting section in the bottom left corner in Zammad next "
"to the avatar icon or your initials:"
msgstr ""

#: ../manage/report-profiles.rst:None
msgid "Menu bar with highlighted reporting"
msgstr ""

#: ../manage/report-profiles.rst:55
msgid ""
"If you can't see the reporting button, you should check the permissions."
msgstr ""

#: ../manage/report-profiles.rst:57
msgid ""
"The reporting screen is separated in different sections, which we describe "
"below:"
msgstr ""

#: ../manage/report-profiles.rst:None
msgid "Screenshot showing different sections in the reporting screen"
msgstr ""

#: ../manage/report-profiles.rst:63
msgid ""
"**Additional filtering** based on the selected profile (see 2). You can "
"filter by status (\"Ticket Count\"), \"Creation Channels\" and "
"\"Communication\" types based on your channels."
msgstr ""

#: ../manage/report-profiles.rst:66
msgid ""
"**Profile switcher**: here you can easily switch between the different "
"profiles, which were created in the admin panel under \"Report Profiles\". "
"The shown tickets and numbers are always limited to the current profile you "
"have selected here."
msgstr ""

#: ../manage/report-profiles.rst:70
msgid ""
"**Time interval/period switcher** and **graph** area: here you can define "
"the interval you want to see (e.g. \"Month\") as well as the time period (e."
"g. \"Jul\")."
msgstr ""

#: ../manage/report-profiles.rst:73
msgid ""
"**Preview and download** section: here you can find a preview of tickets and "
"a download button based on the report profile and your filtering. The "
"download feature provides the tickets in a ``.xlsx`` spreadsheet."
msgstr ""

#: ../manage/report-profiles.rst:77
msgid ""
"The ticket preview and download button are only showing up if you selected a "
"filter based on \"Ticket Count\" (see 1)."
msgstr ""

#: ../manage/report-profiles.rst:80
msgid "Due to technical reasons, the download is limited to 6.000 entries."
msgstr ""

#: ../manage/report-profiles.rst:85
msgid "External Reporting Tools"
msgstr ""

#: ../manage/report-profiles.rst:87
msgid ""
"If the integrated reporting is not enough for you, you can even use third "
"party tools like Grafana! Please have a look at :docs:`Reporting Tools </"
"appendix/reporting-tools-thirdparty.html>` in the system documentation, "
"where you can find more information."
msgstr ""

#: ../manage/roles/admin-permissions.rst:2
msgid "Admin Permissions"
msgstr ""

#: ../manage/roles/admin-permissions.rst:6
#: ../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:18
msgid "Admin permissions in the New Role dialog"
msgstr ""

#: ../manage/roles/admin-permissions.rst:18
msgid "Admin permissions are shown at the top of the New Role dialog..."
msgstr ""

#: ../manage/roles/admin-permissions.rst:26
msgid "Screenshot showing admin settings within Zammad."
msgstr ""

#: ../manage/roles/admin-permissions.rst:26
msgid "...and give users access to the pages of the Admin Panel."
msgstr ""

#: ../manage/roles/admin-permissions.rst:29
msgid ""
"Please be aware that these permissions only grant access to the **settings/"
"configuration** in Zammad. If you want to grant agents access to tickets, "
"see :doc:`agent permissions <agent-permissions>` and :doc:`group permissions "
"<../groups/access-levels>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:38
#: ../manage/roles/agent-permissions.rst:29
#: ../manage/roles/user-preferences-permissions.rst:35
msgid "Permission name"
msgstr ""

#: ../manage/roles/admin-permissions.rst:39
#: ../manage/roles/agent-permissions.rst:30
#: ../manage/roles/user-preferences-permissions.rst:36
msgid "Give access to"
msgstr ""

#: ../manage/roles/admin-permissions.rst:41
msgid "``admin.api``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:42
msgid ":docs:`System > API </api/intro.html>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:44
msgid "``admin.branding``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:45
msgid ":doc:`Settings > Branding </settings/branding>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:47
msgid "``admin.calendar``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:48
msgid ":doc:`Manage > Calendars </manage/calendars>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:49
msgid "Required for :doc:`/manage/slas/index`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:50
msgid "``admin.channel_chat``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:51
msgid ":doc:`Channels > Chat </channels/chat>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:52
msgid "Accessing chat for agents: ``chat.agent``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:53
msgid "``admin.checklist``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:54
msgid ":doc:`Manage > Checklist </manage/checklist>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:56
msgid "``admin.channel_email``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:57
msgid ":doc:`Channels > Email </channels/email/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:59
msgid "``admin.channel_facebook``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:60
msgid ":doc:`Channels > Facebook </channels/facebook>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:61
msgid ""
"Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:62
msgid "``admin.channel_formular``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:63
msgid ":doc:`Channels > Form </channels/form>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:65
msgid "``admin.channel_google``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:66
msgid ":doc:`Channels > Google </channels/google/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:68
msgid "``admin.channel_microsoft365``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:69
msgid ":doc:`Channels > Microsoft 365 </channels/microsoft365/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:71
msgid "``admin.channel_sms``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:72
msgid ":doc:`Channels > SMS </channels/sms>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:74
msgid "``admin.channel_telegram``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:75
msgid ":doc:`Channels > Telegram </channels/telegram>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:76
msgid ""
"Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:77
msgid "``admin.channel_twitter``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:78
msgid ":doc:`Channels > Twitter </channels/twitter-x/twitter>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:79
msgid ""
"Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:80
msgid "``admin.channel_web``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:81
msgid ":doc:`Channels > Web </channels/web>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:83
msgid "``admin.channel_whatsapp``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:84
msgid ":doc:`Channels > Whatsapp </channels/whatsapp/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:86
msgid "``admin.core_workflows``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:87
msgid ":doc:`System > Core Workflows </system/core-workflows>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:89
msgid "``admin.data_privacy``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:90
msgid ":doc:`System > Data Privacy </system/data-privacy>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:91
msgid ""
"🔥 Be careful, it allows users to permanently delete data on the system."
msgstr ""

#: ../manage/roles/admin-permissions.rst:92
msgid "``admin.group``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:93
msgid ":doc:`Manage > Groups </manage/groups/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:95
msgid "``admin.integration``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:96
msgid ":doc:`System > Integrations </system/integrations/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:98
msgid "``admin.knowledge_base``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:99
msgid ":doc:`Manage > Knowledge Base </manage/knowledge-base>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:0
msgid ""
"Accessing knowledge base to read/edit articles: ``knowledge_base.reader``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:0
msgid "and ``knowledge_base.editor``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:0
msgid ""
"Make sure to double-check the answer's :user-docs:`visibility </extras/"
"knowledge-base.html#editing-answers>`."
msgstr ""

#: ../manage/roles/admin-permissions.rst:104
msgid "``admin.macro``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:105
msgid ":doc:`Manage > Macros </manage/macros>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:106
msgid "In some cases, macros may also require ``admin.tag``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:107
msgid "``admin.maintenance``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:108
msgid ":doc:`System > Maintenance </system/maintenance>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:110
msgid "``admin.monitoring``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:111
msgid ":doc:`System > Monitoring </system/monitoring>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:113
msgid "``admin.object``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:114
msgid ":doc:`System > Objects </system/objects>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:116
msgid "``admin.organization``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:117
msgid ":doc:`Manage > Organizations </manage/organizations/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:0
msgid "Agents can access existing organizations"
msgstr ""

#: ../manage/roles/admin-permissions.rst:0
msgid "from the search bar, even without this permission."
msgstr ""

#: ../manage/roles/admin-permissions.rst:0
msgid "They can even edit an organization's name, domain, and notes!"
msgstr ""

#: ../manage/roles/admin-permissions.rst:121
msgid "``admin.overview``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:122
msgid ":doc:`Manage > Overviews</manage/overviews>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:124
msgid "``admin.public_links``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:125
msgid ":doc:`Manage > Public Links </manage/public-links>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:127
msgid "``admin.package``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:128
msgid ":doc:`System > Packages </system/packages>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:130
msgid "``admin.report_profile``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:131
msgid ":doc:`Manage > Report Profiles </manage/report-profiles>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:132
msgid "Access to view reports: ``report``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:133
msgid "``admin.role``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:134
msgid ":doc:`Manage > Roles </manage/roles/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:136
msgid "``admin.scheduler``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:137
msgid ":doc:`Manage > Scheduler </manage/scheduler>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:138
msgid "For automation on tickets"
msgstr ""

#: ../manage/roles/admin-permissions.rst:139
msgid "``admin.security``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:140
msgid ":doc:`Settings > Security </settings/security>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:141
msgid "Settings of Zammad. This also covers third party authentications."
msgstr ""

#: ../manage/roles/admin-permissions.rst:142
msgid "``admin.session``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:143
msgid ":doc:`System > Sessions </system/sessions>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:145
msgid "``admin.setting_system``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:146
msgid ":doc:`Settings > System </settings/system/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:148
msgid "``admin.sla``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:149
msgid ":doc:`Manage > SLAs </manage/slas/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:151
msgid "``admin.system_report``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:152
msgid ":doc:`System > System Report </system/system-report>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:154
msgid "``admin.tag``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:155
msgid ":doc:`Manage > Tags </manage/tags>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:157
msgid "``admin.template``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:158
msgid ":doc:`Manage > Templates </manage/templates>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:160
msgid "``admin.text_module``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:161
msgid ":doc:`Manage > Text Modules </manage/text-modules>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:163
msgid "``admin.ticket``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:164
msgid ":doc:`Settings > Tickets </settings/ticket>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:165
msgid "Does not grant access to :doc:`/misc/composer`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:166
msgid "``admin.ticket_auto_assignment``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:167
msgid ":ref:`Settings > Ticket > Auto Assignment <auto_assignment>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:169
msgid "``admin.ticket_duplicate_detection``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:170
msgid ":ref:`Settings > Ticket > Duplicate Detection <duplicate_detection>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:172
msgid "``admin.ticket_priority``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:173
msgid ":ref:`System > Objects >Ticket Priority <ticket-priority-reference>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:175
msgid "``admin.ticket_state``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:176
msgid ":ref:`System > Objects >Ticket State <ticket-state-reference>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:178
msgid "``admin.time_accounting``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:179
msgid ":doc:`Manage > Time Accounting </manage/time-accounting>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:180
msgid "Also allows the export of timekeeping records."
msgstr ""

#: ../manage/roles/admin-permissions.rst:181
msgid "``admin.translation``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:182
msgid ":doc:`System > Translations </system/translations>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:183
msgid "Also enables inline translation"
msgstr ""

#: ../manage/roles/admin-permissions.rst:184
msgid "``admin.trigger``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:185
msgid ":doc:`Manage > Triggers </manage/trigger>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:187
msgid "``admin.user``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:188
msgid ":doc:`Manage > Users </manage/users/index>`"
msgstr ""

#: ../manage/roles/admin-permissions.rst:0
msgid "Independent from this permission, agents can create and edit"
msgstr ""

#: ../manage/roles/admin-permissions.rst:0
msgid "customers, but they can't modify permission etc."
msgstr ""

#: ../manage/roles/admin-permissions.rst:0
msgid ""
"🏴‍☠️ This permission allows users to :ref:`hijack other user sessions <view-"
"from-users-perspective>` ."
msgstr ""

#: ../manage/roles/admin-permissions.rst:193
msgid "``admin.webhook``"
msgstr ""

#: ../manage/roles/admin-permissions.rst:194
msgid ":doc:`Manage > Webhook </manage/webhook>`"
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:14
msgid "Agent permissions in the New Role dialog"
msgstr ""

#: ../manage/roles/agent-permissions.rst:14
msgid "Agent permissions are shown in the middle of the New Role dialog..."
msgstr ""

#: ../manage/roles/agent-permissions.rst:20
msgid "Sidebar tabs: Overviews, Knowledge Base, Customer Chat, Phone"
msgstr ""

#: ../manage/roles/agent-permissions.rst:20
msgid ""
"...and give users access to new sidebar tabs for communicating with "
"customers."
msgstr ""

#: ../manage/roles/agent-permissions.rst:32
msgid "``chat.agent``"
msgstr ""

#: ../manage/roles/agent-permissions.rst:33
msgid ":user-docs:`Customer Chat </extras/chat.html>`"
msgstr ""

#: ../manage/roles/agent-permissions.rst:34
msgid "Requires configuration of :doc:`Chat Channel </channels/chat>`"
msgstr ""

#: ../manage/roles/agent-permissions.rst:35
msgid "``cti.agent``"
msgstr ""

#: ../manage/roles/agent-permissions.rst:36
msgid ":user-docs:`Caller Log </extras/caller-log.html>`"
msgstr ""

#: ../manage/roles/agent-permissions.rst:37
msgid "Configuration of a CTI integration is required"
msgstr ""

#: ../manage/roles/agent-permissions.rst:38
msgid "``knowledge_base.editor``"
msgstr ""

#: ../manage/roles/agent-permissions.rst:39
msgid "Create/edit privileges"
msgstr ""

#: ../manage/roles/agent-permissions.rst:40
msgid "Editor permissions always include reader permissions."
msgstr ""

#: ../manage/roles/agent-permissions.rst:41
msgid "``knowledge_base.reader``"
msgstr ""

#: ../manage/roles/agent-permissions.rst:42
msgid "Read privileges for internal content"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid "Public articles are always visible."
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid ""
"See :user-docs:`here </extras/knowledge-base.html#granular-category-"
"permissions>` how to set up granular reader permissions for the knowledge "
"base."
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid "Keep in mind that this may be dangerous, as reader permission provides"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid "access to internal answers!"
msgstr ""

#: ../manage/roles/agent-permissions.rst:48
msgid "``report``"
msgstr ""

#: ../manage/roles/agent-permissions.rst:49
msgid ":doc:`Reporting </manage/report-profiles>`"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid "Make sure to never grant this permission to your customers!"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid ""
"Giving customers access to reporting constitutes a serious data breach, as"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid ""
"it includes **all ticket and user information across the entire system**!"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid "Please also note:"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid "1. the feature it enables is not for communicating with customers;"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid "2. the button appears at the *bottom* of the sidebar; and"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid "3. it is typically reserved for admins and supervisors."
msgstr ""

#: ../manage/roles/agent-permissions.rst:57 ../settings/security/base.rst:95
msgid "``ticket.agent``"
msgstr ""

#: ../manage/roles/agent-permissions.rst:58
msgid ":user-docs:`(Agent) Overviews </basics/find-ticket/browse.html>`"
msgstr ""

#: ../manage/roles/agent-permissions.rst:59
msgid "See notes below"
msgstr ""

#: ../manage/roles/agent-permissions.rst:63
msgid "🤔 **What about this table under the permissions tree?**"
msgstr ""

#: ../manage/roles/agent-permissions.rst:0
msgid "Group permission table in Edit Role dialog"
msgstr ""

#: ../manage/roles/agent-permissions.rst:70
msgid ""
"Roles can also include :doc:`group permissions </manage/groups/access-"
"levels>`! The group permission table is shown when there is **more than one "
"active group** in the system and ``ticket.agent`` permission **is selected**."
msgstr ""

#: ../manage/roles/agent-permissions.rst:78
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:82
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 ../manage/users/index.rst:153
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 "💡 **LDAP/Active Directory users:**"
msgstr ""

#: ../manage/roles/index.rst:18
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:25
msgid "What Is a Role?"
msgstr ""

#: ../manage/roles/index.rst:27
msgid ""
"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. You can think of roles as a kind of a collection of permissions."
msgstr ""

#: ../manage/roles/index.rst:32
msgid "So what exactly are permissions, then?"
msgstr ""

#: ../manage/roles/index.rst:39
msgid "List of permissions in the New Role dialog"
msgstr ""

#: ../manage/roles/index.rst:39
msgid ""
"The ``admin.calendar`` permission gives you access to the **Manage > "
"Calendars** admin panel."
msgstr ""

#: ../manage/roles/index.rst:42
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:45
msgid "``chat.agent``: respond to live chat messages"
msgstr ""

#: ../manage/roles/index.rst:46
msgid "``ticket.agent``: update tickets"
msgstr ""

#: ../manage/roles/index.rst:47
msgid "``admin.user``: access the **Manage > Users** admin panel"
msgstr ""

#: ../manage/roles/index.rst:48
msgid "``knowledge_base.editor``: create/edit knowledge base articles"
msgstr ""

#: ../manage/roles/index.rst:50
msgid ""
"Zammad has dozens of these permissions, which is a lot to keep track of. So "
"instead of assigning a bunch of permissions to different users, the idea is "
"to assign permissions to roles. And each user has an assigned role."
msgstr ""

#: ../manage/roles/index.rst:54
msgid ""
"This makes creating user accounts for new agents a whole lot simpler, and it "
"also makes it easier to assign a new permission to a role and say \"All "
"existing agents can do *that* now, too.\""
msgstr ""

#: ../manage/roles/index.rst:58
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:62
msgid "And to do that, you'll need to know what each permission does."
msgstr ""

#: ../manage/roles/index.rst:64
msgid "Users can have both \"agent\" and \"customer\" roles at the same time!"
msgstr ""

#: ../manage/roles/index.rst:66
msgid ""
"Why would you want this? Agents get :doc:`overviews </manage/overviews>` of "
"all the tickets they're *assigned to* (among others), 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:73
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:79
msgid "Reference Guide: Permissions"
msgstr ""

#: ../manage/roles/index.rst:88
msgid ""
"Broadly speaking, there are four types of permission groups. Click on each "
"to go to the detailed list of granular permissions. You can either select "
"the whole permission group (e.g. ``admin``) or a subset of it (e.g. ``admin."
"text_module``)."
msgstr ""

#: ../manage/roles/index.rst:94
msgid ":doc:`🛡️ Admin <admin-permissions>`"
msgstr ""

#: ../manage/roles/index.rst:94
msgid "For access to each page of the admin panel"
msgstr ""

#: ../manage/roles/index.rst:97
msgid ":doc:`🕵️ Agent <agent-permissions>`"
msgstr ""

#: ../manage/roles/index.rst:97
msgid "For access to customer communications"
msgstr ""

#: ../manage/roles/index.rst:102
msgid "👤 Customer"
msgstr ""

#: ../manage/roles/index.rst:100
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:106
msgid ":doc:`🎛️ User Preferences <user-preferences-permissions>`"
msgstr ""

#: ../manage/roles/index.rst:105
msgid ""
"For access to your own :user-docs:`user profile </extras/profile-and-"
"settings.html>`"
msgstr ""

#: ../manage/roles/index.rst:109
msgid "Role Details"
msgstr ""

#: ../manage/roles/index.rst:123
msgid "Default at Signup"
msgstr ""

#: ../manage/roles/index.rst:112
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:120
msgid ""
"The default role is identified in the overview of the **Manage > Roles** "
"admin panel."
msgstr ""

#: ../manage/roles/index.rst:123
msgid "🙅 **Default roles should never provide admin/agent permissions.**"
msgstr ""

#: ../manage/roles/index.rst:126
msgid ""
"Roles can't be deleted but set to inactive. If you do so, all users loose "
"the permissions of this role. If this inactive role is the only one of a "
"user, this account isn't able to do anything in Zammad. The login is still "
"possible."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:2
msgid "User Preferences Permissions"
msgstr ""

#: ../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:20
msgid "User preferences permissions in the New Role dialog"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:20
msgid ""
"User preferences permissions are shown at the bottom of the New Role "
"dialog..."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:28
msgid "User profile page"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:28
msgid ""
"...and give users access to the pages of their :user-docs:`User Profile </"
"extras/profile-and-settings.html>`."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:38
msgid "``user_preferences.access_token``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Generate API tokens to control"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Zammad via :docs:`REST API </api/intro.html>`"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Generated tokens will never have more permissions"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "than the user that generated them."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:43
msgid "``user_preferences.appearance``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:44
msgid "Appearance configuration"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Users can switch between dark, light and"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "automatic mode."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:47
msgid "``user_preferences.avatar``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:48
msgid "Avatar settings"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:49
msgid "Override the default Gravatar with a custom avatar"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:50
msgid "``user_preferences.calendar``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:51
msgid "Configure the calendar feed"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:53
msgid "``user_preferences.device``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:54
msgid "Manage device login sessions"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Revoking this permission disables"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "“Login detected from a new location” emails."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "To learn more, see :doc:`/manage/trigger/system-notifications`."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:58
msgid "``user_preferences.language``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:59
msgid "Configure the UI locale/language"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:61
msgid "``user_preferences.linked_accounts``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:62
msgid "Account linking"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Manually link accounts after signing in"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid ""
"with :doc:`third-party authentication </settings/security/third-party>`."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid ""
"Note: If :ref:`automatic account linking <automatic-account-linking>` fails, "
"this"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "is the only way users can utilize third-party logins."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:67
msgid "``user_preferences.notifications``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Configuration of ticket"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
#: ../settings/branding.rst:27 ../settings/branding.rst:39
msgid "notifications"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Agents only receive ticket notifications for"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid ""
":doc:`groups they have “full” access to </manage/groups/access-levels>`."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Customers can't receive ticket notifications at all."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:73
msgid "``user_preferences.out_of_office``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Designate a substitute for"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "out-of-office hours"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "This does **not** grant that person the permissions /"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid ":doc:`group access levels </manage/groups/access-levels>` of the agent"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "they're replacing."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:79
msgid "``user_preferences.overview_sorting``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Allow users to define their own"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "overview order."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Optional permission; disabled by default."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "The order your user chooses here cannot be"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "overwritten by admins. Renaming or resorting"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "overviews has no effect on custom orders."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:86
msgid "``user_preferences.password``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:87
msgid "Change account password"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Make sure to **revoke this permission** for all your users"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "when using a third-party identity server (like LDAP) as"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "your only allowed authentication method."
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:91
msgid "``user_preferences.two_factor_authentication``"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "Allow users to setup and configure"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "their two factor authentication"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid ""
":doc:`Two factor authentication </settings/security/two-factor>` has to be "
"enabled"
msgstr ""

#: ../manage/roles/user-preferences-permissions.rst:0
msgid "that users can setup and configure it."
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 objects they should affect, and then configure "
"the actions that you want to be executed on these objects."
msgstr ""

#: ../manage/scheduler.rst:19
msgid ""
"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/"
"variables` to build highly-customized email templates."
msgstr ""

#: ../manage/scheduler.rst:22
msgid ""
"Schedulers only perform ``2000`` objects per run. This is a security "
"function in case you accidentally misconfigured the scheduler."
msgstr ""

#: ../manage/scheduler.rst:26
msgid "Add a New Scheduler"
msgstr ""

#: ../manage/scheduler.rst:28
msgid ""
"Create a new scheduler job by clicking on the \"New scheduler\" button in "
"the top right corner. Then Zammad presents a dialog where you can create "
"your own one."
msgstr ""

#: ../manage/scheduler.rst:31
msgid "Example:"
msgstr ""

#: ../manage/scheduler.rst:None
msgid "Screenshot showing dialog of creating a new scheduler job"
msgstr ""

#: ../manage/scheduler.rst:39
msgid "Choose a name for the scheduler."
msgstr ""

#: ../manage/scheduler.rst:43
msgid "When should the job run?"
msgstr ""

#: ../manage/scheduler.rst:42
msgid ""
"Choose the points in time when the scheduler should run. It depends on the "
"configured :doc:`timezone in Zammad </settings/branding>`."
msgstr ""

#: ../manage/scheduler.rst:47 ../system/core-workflows/how-do-they-work.rst:15
msgid "Object"
msgstr ""

#: ../manage/scheduler.rst:46
msgid ""
"Choose in which object context the scheduler should be executed. Possible "
"objects are: **Organization**, **Ticket** and **User**."
msgstr ""

#: ../manage/scheduler.rst:53
msgid "Conditions for affected objects"
msgstr ""

#: ../manage/scheduler.rst:50
msgid ""
"Determine the object attributes (conditions) to limit on which objects the "
"actions configured in step 5 are to be performed."
msgstr ""

#: ../manage/scheduler.rst:56
msgid ""
"This list previews some objects that your conditions are matching and shows "
"a total of how many objects are being matched. Use this to double-check the "
"entered conditions."
msgstr ""

#: ../manage/scheduler.rst:60
msgid ""
"Please be aware that the preview and displayed number is just based on the "
"currently selected condition. It doesn't necessarily represent the objects "
"for execution at the defined time."
msgstr ""

#: ../manage/scheduler.rst:81
msgid "Execute changes on objects"
msgstr ""

#: ../manage/scheduler.rst:65
msgid ""
"Determine the changes to be made to the object. The possible changes depend "
"on the selected object context. Be aware that a related object context may "
"not be available (e.g. to perform ticket actions from a user context based "
"scheduler)."
msgstr ""

#: ../manage/scheduler.rst:72
msgid ""
"🔥 Schedulers with *Action: Delete immediately* and *Action: Add a data "
"privacy deletion task* are dangerous and should be used with care! If "
"executed, the objects are deleted and no rollback is possible."
msgstr ""

#: ../manage/scheduler.rst:76
msgid ""
"**Delete immediately** will delete the ticket at the runtime of the job "
"*without any hint* in the UI."
msgstr ""

#: ../manage/scheduler.rst:79
msgid ""
"**Add a data privacy deletion task** will create a data privacy deletion "
"task for the object at the runtime of the job. That means it is visible in "
"Zammad's :doc:`data privacy panel </system/data-privacy>`."
msgstr ""

#: ../manage/scheduler.rst:85
msgid "Disable notifications"
msgstr ""

#: ../manage/scheduler.rst:84
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:94 ../settings/branding.rst:27
msgid "Locale"
msgstr ""

#: ../manage/scheduler.rst:88 ../manage/scheduler.rst:97
msgid ""
"This can be activated with the switch labeled \"Localization of execution "
"changes\"."
msgstr ""

#: ../manage/scheduler.rst:91
msgid ""
"Set a desired language, in which the output of variables is translated into "
"by using the ``t`` function. For more information, please have a look at the "
"explanation in the :ref:`variables section <variable_localization>`."
msgstr ""

#: ../manage/scheduler.rst:103 ../settings/branding.rst:44
msgid "Timezone"
msgstr ""

#: ../manage/scheduler.rst:100
msgid ""
"Similar as for the \"Locale\" setting, you can define a time zone, which is "
"applied to the output of time stamp variables. For more information, please "
"have a look at the explanation in the :ref:`variables section "
"<variable_localization>`."
msgstr ""

#: ../manage/scheduler.rst:106
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 objects."
msgstr ""

#: ../manage/scheduler.rst:111
msgid "With this setting you can enable/disable the scheduler."
msgstr ""

#: ../manage/scheduler.rst:113
msgid "The scheduler shown in the screenshot would have the following effects:"
msgstr ""

#: ../manage/scheduler.rst:115
msgid ""
"Every workday (Monday to Friday) at 9:00 a.m. (*Europe / Berlin UTC+1*), all "
"tickets which:"
msgstr ""

#: ../manage/scheduler.rst:118
msgid "are not closed or merged, and"
msgstr ""

#: ../manage/scheduler.rst:119
msgid "are assigned to the Sales group, and"
msgstr ""

#: ../manage/scheduler.rst:120
msgid "whose escalation was 30 minutes ago"
msgstr ""

#: ../manage/scheduler.rst:122
msgid "will be:"
msgstr ""

#: ../manage/scheduler.rst:124
msgid "assigned to Emma, and"
msgstr ""

#: ../manage/scheduler.rst:125
msgid "have their priority changed to 3 high."
msgstr ""

#: ../manage/scheduler.rst:127
msgid ""
"As a supervisor in the Sales group, this enables Emma to intercept and "
"process escalated tickets."
msgstr ""

#: ../manage/scheduler.rst:130
msgid ""
"Emma will not receive notifications when the scheduler assigns her these "
"tickets."
msgstr ""

#: ../manage/slas/how-do-they-work.rst:2
msgid "How Do SLAs Work"
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 dialog 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, :docs:`our console documentation </admin/console/working-on-"
"ticket-articles.html#count-public-notes-toward-slas>` tells you how."
msgstr ""

#: ../manage/slas/how-do-they-work.rst:26
msgid "Give your SLA a meaningful name to quickly see what or who is affected."
msgstr ""

#: ../manage/slas/how-do-they-work.rst:31
msgid "Ticket selector"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:29
msgid "Specify the conditions on which tickets this SLA should apply to."
msgstr ""

#: ../manage/slas/how-do-they-work.rst:34
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:42
#: ../misc/object-conditions/basics.rst:80
msgid "Calendar"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:38
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:41
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:93
msgid "SLA Times"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:45
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:55
msgid "First Response"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:50
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:53
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:71
msgid "Update Time"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:58
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:67
msgid "between agent updates"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:63
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:67
msgid "Be aware that this setting can be quite stressful for your agents!"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:71
msgid "for an agent to respond"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:70
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:78
msgid "Solution Time"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:74
msgid ""
"Time frame for solving the problem (setting the ticket to a closed state "
"type)."
msgstr ""

#: ../manage/slas/how-do-they-work.rst:77
msgid ""
"This escalation timing *does not* care about ticket responses. It's simply "
"being calculated from the ticket creation."
msgstr ""

#: ../manage/slas/how-do-they-work.rst:80
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:85
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:89
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:97
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:101
msgid "by searching"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:102
msgid ":doc:`/manage/trigger`"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:103
msgid ":doc:`/manage/scheduler`"
msgstr ""

#: ../manage/slas/how-do-they-work.rst:104
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
#: ../settings/security/third-party.rst:82 ../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:2
msgid "SLA Example"
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
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 "**Attributes**"
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:90
#: ../system/core-workflows/learn-by-example.rst:103
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-docs:`user documentation </basics/service-ticket/"
"settings/tags.html>`."
msgstr ""

#: ../manage/tags.rst:14
msgid "Tag-Overviews"
msgstr ""

#: ../manage/tags.rst:16
msgid "You can list all the marked tickets by tag in different ways:"
msgstr ""

#: ../manage/tags.rst:18
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:22
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:29
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:35
msgid ""
"For more information about the individual tags, just click on the blue "
"counter:"
msgstr ""

#: ../manage/tags.rst:40
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:47
msgid "Tag Management Area"
msgstr ""

#: ../manage/tags.rst:49
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:53
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:50
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:54
msgid ""
"Zammad allows you to clone existing templates and continue your new template "
"from there."
msgstr ""

#: ../manage/templates.rst:57
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:61
msgid ""
"If you no longer require a specific template, use *⋮ Actions* in the list "
"and choose *Delete*."
msgstr ""

#: ../manage/templates.rst:64
msgid "Be aware that the deletion is permanent."
msgstr ""

#: ../manage/text-modules.rst:2
msgid "Text Modules"
msgstr ""

#: ../manage/text-modules.rst:4
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:8
msgid ""
"Beside text modules Zammad also allows you to use :user-docs:`Ticket "
"Templates for ticket creation </advanced/ticket-templates.html>`."
msgstr ""

#: ../manage/text-modules.rst:13
msgid "Here you can add new text modules, delete or edit them."
msgstr ""

#: ../manage/text-modules.rst:15
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:20
msgid ""
"If needed, you can restrict text modules to specific groups. With this, you "
"can easily keep text module lists short and dedicate specific texts to where "
"they belong."
msgstr ""

#: ../manage/text-modules.rst:24
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:31
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:35
msgid ""
"To use the text modules in a ticket, you can use ``::`` too! You can find "
"more information on how to use text modules in our :user-docs:`user "
"documentation </advanced/text-modules.html>`."
msgstr ""

#: ../manage/text-modules.rst:57
msgid ""
"The example text modules below use :doc:`/misc/variables` to dynamically "
"insert information like the customer's or agent's names."
msgstr ""

#: ../manage/text-modules.rst:60
msgid "**Examples of snippets are**::"
msgstr ""

#: ../manage/text-modules.rst:70
msgid "Of course you can also use multi line snippets."
msgstr ""

#: ../manage/text-modules.rst:73
msgid "Delete or Clone Text Modules"
msgstr ""

#: ../manage/text-modules.rst:75
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:81
msgid ""
"When cloning, text modules with all attributes are duplicated and can be "
"edited later."
msgstr ""

#: ../manage/text-modules.rst:85
msgid "Import of Text Modules via CSV File"
msgstr ""

#: ../manage/text-modules.rst:87
msgid ""
"With the import action you can download a sample CSV file and upload your "
"own CSV file."
msgstr ""

#: ../manage/text-modules.rst:90
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 the time accounting (turn on the switch on the top left side of the "
"page)."
msgstr ""

#: ../manage/time-accounting.rst:None
msgid "Time Accounting Management Screen in Zammad"
msgstr ""

#: ../manage/time-accounting.rst:12
#: ../settings/security/two-factor/authenticator-app.rst:10
#: ../settings/security/two-factor/security-keys.rst:10
msgid "How it Works"
msgstr ""

#: ../manage/time-accounting.rst:17
msgid ""
"Zammad's time accounting uses ticket **Selector** (filter) to check if a "
"ticket is considered for the time accounting or not. If a ticket is "
"applicable, Zammad will request the agent to provide how much time was "
"needed to process the current ticket step."
msgstr ""

#: ../manage/time-accounting.rst:22
msgid ""
"In order for Zammad to bring up the time accounting dialog to an agent, the "
"agent has to update the ticket together with an article of any type. The "
"article part is mandatory."
msgstr ""

#: ../manage/time-accounting.rst:26
msgid ""
"However, the time accounting dialog is not mandatory and can be canceled by "
"your agents if needed. You cannot enforce time accounting."
msgstr ""

#: ../manage/time-accounting.rst:29
msgid ""
"If a ticket is no longer considered for the time accounting, the already "
"accounted time will be preserved."
msgstr ""

#: ../manage/time-accounting.rst:34
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 Selector"
msgstr ""

#: ../manage/time-accounting.rst:45
msgid ""
"By default, agents account time as a unitless numerical input. However, it "
"is possible to show a specific unit by configuring **Unit** setting, which "
"provides several options:"
msgstr ""

#: ../manage/time-accounting.rst:49
msgid "no unit"
msgstr ""

#: ../manage/time-accounting.rst:50
msgid "Default behavior, no unit is shown next to the time value."
msgstr ""

#: ../manage/time-accounting.rst:51
msgid "hour(s)"
msgstr ""

#: ../manage/time-accounting.rst:52
msgid "Shows ``hour(s)`` as the unit next to the time value."
msgstr ""

#: ../manage/time-accounting.rst:53
msgid "quarter-hour(s)"
msgstr ""

#: ../manage/time-accounting.rst:54
msgid "Shows ``quarter-hour(s)`` as the unit next to the time value."
msgstr ""

#: ../manage/time-accounting.rst:55
msgid "minute(s)"
msgstr ""

#: ../manage/time-accounting.rst:56
msgid "Shows ``minute(s)`` as the unit next to the time value."
msgstr ""

#: ../manage/time-accounting.rst:58
msgid "custom unit"
msgstr ""

#: ../manage/time-accounting.rst:58
msgid "Shows a custom unit that can be specified as free input."
msgstr ""

#: ../manage/time-accounting.rst:None
msgid "Time Accounting Unit"
msgstr ""

#: ../manage/time-accounting.rst:65
msgid "The configurable time accounting unit is used only for display!"
msgstr ""

#: ../manage/time-accounting.rst:67
msgid ""
"No numerical transformation will be applied to the values, the unit is "
"merely used to indicate to the agents in which units their time is "
"accounted. The original time values will be preserved."
msgstr ""

#: ../manage/time-accounting.rst:0
msgid "Time Accounting Unit when Recording"
msgstr ""

#: ../manage/time-accounting.rst:76
msgid "Activity Types"
msgstr ""

#: ../manage/time-accounting.rst:78
msgid ""
"**Activity Types** can be used to group the different ticket time accounting "
"entries together. For example, entries that are relevant to a \"Billing\" "
"type."
msgstr ""

#: ../manage/time-accounting.rst:None
msgid "Time Accounting Activity Types"
msgstr ""

#: ../manage/time-accounting.rst:85
msgid ""
"When you enable the recording of the **Activity Type**, the agents will be "
"able to select a type from this list."
msgstr ""

#: ../manage/time-accounting.rst:None
msgid "Time Accounting Activity Type Selection for Agents"
msgstr ""

#: ../manage/time-accounting.rst:92
msgid ""
"Additionally, a column with an associated activity type will be rendered for "
"an entry in the **Activity** table under the **Accounted Time** tab."
msgstr ""

#: ../manage/time-accounting.rst:95
msgid ""
"You can manage available activity types in this screen like any other Zammad "
"object. Only active types will be available for the selection when recording "
"new times. If an activity type has accounted time, it is still displayed in "
"tickets and included in the accounted time overview."
msgstr ""

#: ../manage/time-accounting.rst:None
msgid "New Time Accounting Activity Type Dialog"
msgstr ""

#: ../manage/time-accounting.rst:104
msgid ""
"Activity types can be set as default, and in that case they will be pre-"
"selected for the agents when they are asked to account their time. It is "
"also possible to unset default activity type, in which case no type will be "
"pre-selected and the agents can make their choice."
msgstr ""

#: ../manage/time-accounting.rst:110
msgid "Accounted Time"
msgstr ""

#: ../manage/time-accounting.rst:112
msgid ""
"Under the **Accounted Time** tab, Zammad provides a section for reviewing "
"all accounted times for your tickets. Accounted times are displayed per "
"years and months."
msgstr ""

#: ../manage/time-accounting.rst:116
msgid ""
"If you have tickets that are overlapping several months, you can "
"differentiate by *time units* and *time units total* (e.g. to allow partial "
"billing) in the downloaded file."
msgstr ""

#: ../manage/time-accounting.rst:127
msgid "Select the right month"
msgstr ""

#: ../manage/time-accounting.rst:121
msgid ""
"Usually you want to bill accounted time of other months than the current "
"one. Just select the relevant year and month to receive the accounted times "
"and ticket information."
msgstr ""

#: ../manage/time-accounting.rst:0
msgid "Screenshot showing a selection for year and month on time accounting"
msgstr ""

#: ../manage/time-accounting.rst:197
msgid "Tickets and their accounted time"
msgstr ""

#: ../manage/time-accounting.rst:130
msgid ""
"Zammad allows you to receive the accounted information just like you need "
"them. For this you currently have four options to review and also download "
"the relevant data as CSV."
msgstr ""

#: ../manage/time-accounting.rst:134
msgid ""
"To download the CSV data, use the download button right next to each heading "
"(e.g. \"Ticket\")."
msgstr ""

#: ../manage/time-accounting.rst:137
msgid "This can also be automated with API calls."
msgstr ""

#: ../manage/time-accounting.rst:140
msgid ""
"Only the first 20 entries are shown for each table. To see all of them, "
"simply download the records in CSV."
msgstr ""

#: ../manage/time-accounting.rst:157
msgid "Activity"
msgstr ""

#: ../manage/time-accounting.rst:144
msgid ""
"This filter works similar to the ticket filter, with one exception: You'll "
"find each *individual* time accounting step of your agents. This is what "
"you'd also see in the ticket's history before Zammad 5.2."
msgstr ""

#: ../manage/time-accounting.rst:148 ../manage/time-accounting.rst:162
#: ../manage/time-accounting.rst:179
msgid "In this list you'll see the following ticket information:"
msgstr ""

#: ../manage/time-accounting.rst:150 ../manage/time-accounting.rst:164
#: ../settings/ticket.rst:91
msgid "Number"
msgstr ""

#: ../manage/time-accounting.rst:152 ../manage/time-accounting.rst:166
#: ../manage/time-accounting.rst:183 ../manage/time-accounting.rst:181
#: ../misc/object-conditions/basics.rst:36
#: ../misc/object-conditions/basics.rst:90
#: ../misc/object-conditions/basics.rst:172
msgid "Customer"
msgstr ""

#: ../manage/time-accounting.rst:153 ../manage/time-accounting.rst:167
#: ../manage/time-accounting.rst:182
msgid "Organization of customer (if applicable)"
msgstr ""

#: ../manage/time-accounting.rst:154
msgid "Agent that accounted the time"
msgstr ""

#: ../manage/time-accounting.rst:155
msgid "Time units accounted in the current activity"
msgstr ""

#: ../manage/time-accounting.rst:156
msgid "Activity type (if enabled)"
msgstr ""

#: ../manage/time-accounting.rst:157 ../manage/time-accounting.rst:171
#: ../manage/webhook/log.rst:29
msgid "Created at"
msgstr ""

#: ../manage/time-accounting.rst:172 ../misc/object-conditions/basics.rst:25
#: ../misc/object-conditions/basics.rst:91
#: ../misc/object-conditions/basics.rst:127
#: ../misc/object-conditions/basics.rst:140
#: ../misc/object-conditions/basics.rst:158
#: ../misc/object-conditions/basics.rst:174
#: ../misc/object-conditions/basics.rst:182
#: ../misc/object-conditions/basics.rst:192 ../misc/variables/ticket.rst:2
#: ../settings/ticket.rst:2
msgid "Ticket"
msgstr ""

#: ../manage/time-accounting.rst:160
msgid "This filter contains all relevant tickets from the selected month."
msgstr ""

#: ../manage/time-accounting.rst:168
msgid "Agent currently assigned (ticket owner)"
msgstr ""

#: ../manage/time-accounting.rst:169 ../manage/time-accounting.rst:183
msgid "Time units accounted in the current month"
msgstr ""

#: ../manage/time-accounting.rst:170
msgid "Time units total (time accounted during ticket life)"
msgstr ""

#: ../manage/time-accounting.rst:172
msgid "Closed at (if applicable)"
msgstr ""

#: ../manage/time-accounting.rst:175
msgid ""
"This provides you a per user filter on accounted time units. Each user has a "
"total of time accounted in the current month (over all applicable tickets)."
msgstr ""

#: ../manage/time-accounting.rst:191 ../misc/object-conditions/basics.rst:27
#: ../misc/object-conditions/basics.rst:116
#: ../misc/object-conditions/basics.rst:147 ../settings/branding.rst:13
msgid "Organization"
msgstr ""

#: ../manage/time-accounting.rst:186
msgid ""
"This provides a list of all organizations where customers have caused "
"accounted time in that month."
msgstr ""

#: ../manage/time-accounting.rst:189
msgid ""
"You can also see entries for customers that are part of a primary "
"organization. Users without an organization can be found in the Customer "
"filter."
msgstr ""

#: ../manage/time-accounting.rst:0
msgid "Time accounting view with time accounted filters"
msgstr ""

#: ../manage/time-accounting.rst:197
msgid ""
"Each heading allows you to download the CSV versions of the provided view "
"via the download button next to it."
msgstr ""

#: ../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. For time-based or recurring automation workflows, try :doc:"
"`schedulers </manage/scheduler>` instead."
msgstr ""

#: ../manage/trigger.rst:8
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:15
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:21
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:2
msgid "How Do Trigger Work"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:4
msgid "Triggers consist of three parts:"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:6
msgid "**Activators:** define \"when the question is asked?\""
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:7
msgid "**Conditions:** answer the question \"when should this trigger fire?\""
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:8
msgid "**Actions:** answer the question \"what should happen when it does?\""
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:10
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:14
msgid "**🤓 Emails can adjust some behavior on their own**"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:16
msgid "See :doc:`/channels/email/email-headers` for more information."
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:24
#: ../manage/webhook/examples/generic-notifications-trigger.rst:32
#: ../misc/object-conditions/basics.rst:67
#: ../system/core-workflows/how-do-they-work.rst:70 ../system/sessions.rst:52
msgid "Action"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:26
msgid ""
"The execution 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:30
msgid "Action activator may evaluate **conditions** in two modes:"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:38
msgid "**Selective** execution"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:33
msgid ""
"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:36
msgid ""
"**Example:** 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:46
msgid "**Always** execution"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:41
msgid ""
"checks if the current state of the ticket in question matches conditions."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:44
msgid ""
"**Example:** 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:49
msgid "Time Event"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:51
msgid ""
"The execution 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:54
msgid ""
"This 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:57
msgid "When creating a trigger, choose activator here:"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:62
#: ../system/core-workflows/how-do-they-work.rst:37
msgid "Conditions"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:64
msgid "When creating a trigger, define your conditions here:"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:68
msgid "Trigger conditions must match as configured for the trigger to fire."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:75
msgid "When creating a trigger, define your changes here:"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:79
msgid ""
"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/"
"variables`, which can be used to build highly-customized message templates."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:83
msgid ""
"A trigger can do the following things once its conditions have been met:"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:94
msgid "Modify the ticket"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:86
msgid ""
"Examples: escalate its priority, close it, reassign it, rename it, add tags, "
"subscribe and unsubscribe specific/all users, etc."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:89
msgid ""
"Date & time attributes (like **Pending till**) can be specified in "
"*absolute* or *relative* terms."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:92
msgid ""
"You can also combine static text with placeholders for text fields. Remember "
"that the placeholders' values have to be known during trigger runtime. Learn "
"more about :doc:`/misc/variables`."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:105
msgid "Send an email or SMS"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:97
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:100
msgid ""
"Sending emails allows you to include the attachments of the triggering "
"article if required."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:103
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 ":doc:`Fire a webhook </manage/webhook>`"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:108
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:112
msgid "Add internal or public notes to the ticket"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:111
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:117
msgid "Localization of Execution Changes"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:119
msgid ""
"The system locale and timezone predefines a default format of date and "
"timestamp replacement variables. These settings are customizable for "
"triggers."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:0
msgid "Screenshot showing localization section of trigger dialog"
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:126
msgid ""
"Best practice is to create single separated localized triggers for each "
"language/timezone and execute them based on user or organization attributes."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:129
msgid ""
"The format and timezone of date and timestamp replacement variables is "
"customizable by the use of the ``dt()`` method. Further on the ``t()`` "
"method can be used to translated string replacement variables according to "
"the selected locale language."
msgstr ""

#: ../manage/trigger/how-do-they-work.rst:131
msgid ""
"For usage of the ``t()`` and ``dt()`` method, please follow the instructions "
"in the :ref:`variables section <variable_localization>`."
msgstr ""

#: ../manage/trigger/learn-by-example.rst:2
msgid "Trigger Examples"
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 ""
"To learn about triggers in detail, first go to :doc:`/manage/trigger/how-do-"
"they-work`."
msgstr ""

#: ../manage/trigger/learn-by-example.rst:10
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:26
msgid ""
"Send an auto-reply email to any customer who creates a ticket via web, if "
"the detected language is English:"
msgstr ""

#: ../manage/trigger/learn-by-example.rst:33
msgid "📨 **Not all automated messages come from triggers!**"
msgstr ""

#: ../manage/trigger/learn-by-example.rst:35
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 </manage/trigger/"
"system-notifications>`."
msgstr ""

#: ../manage/trigger/limitations.rst:4
msgid ""
"Triggers are one way of automated actions. In addition, there are also :doc:"
"`scheduler </manage/scheduler>` and :doc:`postmaster filter </channels/email/"
"filters>` based automation. Make sure to have a look at those, too. They can "
"be more suitable, depending on your use case."
msgstr ""

#: ../manage/trigger/limitations.rst:10
msgid "Limitations of triggers:"
msgstr ""

#: ../manage/trigger/limitations.rst:12
msgid ""
"Triggers are executed when a ticket is updated via clicking the \"Update\" "
"button. Changing a value without updating the ticket (e.g. setting a tag) "
"will not execute the trigger."
msgstr ""

#: ../manage/trigger/limitations.rst:15
msgid ""
"Triggers are always affecting the last article of a ticket. This means you "
"can't run triggers based on older articles."
msgstr ""

#: ../manage/trigger/limitations.rst:17
msgid ""
"Triggers always handle the current ticket attributes and the article (if "
"applicable) that causes the trigger to fire. A related object context might "
"not be available for performing changes."
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 ""
"Users can be managed individually via UI, via API or even synchronized with "
"third-party directory services."
msgstr ""

#: ../manage/users/index.rst:7
msgid ""
"Zammad creates a user for everyone who communicates with the system. That "
"means even customers get their own accounts, even if they don't use it to "
"log in to Zammad."
msgstr ""

#: ../manage/users/index.rst:16
msgid "The simplest way to manage users is directly in the Admin Panel."
msgstr ""

#: ../manage/users/index.rst:24
msgid "Learn more about managing users..."
msgstr ""

#: ../manage/users/index.rst:19
msgid ":doc:`via the Admin Panel <via-the-admin-panel>`"
msgstr ""

#: ../manage/users/index.rst:20
msgid ":doc:`via CSV import <via-csv-import>`"
msgstr ""

#: ../manage/users/index.rst:21
msgid ""
":doc:`via LDAP/Active Directory integration </system/integrations/ldap/"
"index>`"
msgstr ""

#: ../manage/users/index.rst:22
msgid ":doc:`via Exchange integration </system/integrations/exchange>`"
msgstr ""

#: ../manage/users/index.rst:23
msgid ":docs:`via REST API </api/intro.html>`"
msgstr ""

#: ../manage/users/index.rst:24
msgid ":ref:`via invitation email <invite-agents>`"
msgstr ""

#: ../manage/users/index.rst:36
msgid "Reference Guide: User Details"
msgstr ""

#: ../manage/users/index.rst:38
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:46
msgid "The edit user dialog, showing the various user detail fields"
msgstr ""

#: ../manage/users/index.rst:46
msgid "User details can be set in the **New/Edit User** dialog."
msgstr ""

#: ../manage/users/index.rst:48
msgid "🕵️ **Admins aren't the only ones who can change these settings.**"
msgstr ""

#: ../manage/users/index.rst:50
msgid ""
"In most cases, agents can, too (using the :user-docs:`new ticket dialog </"
"basics/service-ticket/create.html>`, :user-docs:`search bar </basics/find-"
"ticket/search.html>` or the :user-docs:`ticket pane </extras/customers."
"html>`)."
msgstr ""

#: ../manage/users/index.rst:69
msgid "👤 Login"
msgstr ""

#: ../manage/users/index.rst:57
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:64
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:67
msgid ""
"This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:"
"`Zammad console </admin/console.html>`, the :docs:`REST API </api/intro."
"html>`, or :doc:`CSV import <via-csv-import>`."
msgstr ""

#: ../manage/users/index.rst:74
msgid "🔑 Password"
msgstr ""

#: ../manage/users/index.rst:72
msgid ""
"Yes, administrators really do have the power to change other users' "
"passwords."
msgstr ""

#: ../manage/users/index.rst:74
msgid "(Agents do not, though.)"
msgstr ""

#: ../manage/users/index.rst:83
msgid "🏢 Organization"
msgstr ""

#: ../manage/users/index.rst:77
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:82
msgid ""
"Please note that the organization has to exist before it can be assigned. To "
"add one, go to **Manage > Organizations** in the Admin Panel."
msgstr ""

#: ../manage/users/index.rst:100
msgid "🏤 Secondary Organizations"
msgstr ""

#: ../manage/users/index.rst:86
msgid ""
"This option allows you to assign more organizations, in addition to the "
"user's primary organization."
msgstr ""

#: ../manage/users/index.rst:89
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:92
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:97
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:100
msgid "30-40 organizations at maximum *should* be good enough."
msgstr ""

#: ../manage/users/index.rst:103
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:113
msgid "VIPs are displayed with a crown above their avatars."
msgstr ""

#: ../manage/users/index.rst:118
msgid ""
"😵 **Are you using the Note field to keep track of your own \"custom\" user "
"attributes?**"
msgstr ""

#: ../manage/users/index.rst:121
msgid "Wish you could add your own fields to the New/Edit User dialog?"
msgstr ""

#: ../manage/users/index.rst:126
msgid ""
"Inactive users aren't able to login anymore. However, they can still be used "
"in different places in Zammad (e.g. as ticket customer, in conditions in "
"triggers and schedulers)."
msgstr ""

#: ../manage/users/index.rst:130
msgid "What's the difference between deactivating and deleting a user?"
msgstr ""

#: ../manage/users/index.rst:132
msgid ""
"There is no way to restore a deleted user; inactive users can be reactivated "
"at any time."
msgstr ""

#: ../manage/users/index.rst:135
msgid ""
"When a user is deleted, all their associated tickets are lost, as well; "
"deactivating a user keeps all associated tickets intact."
msgstr ""

#: ../manage/users/index.rst:138
msgid ""
"Inactive users still appear in search results and can be used as a ticket "
"customer:"
msgstr ""

#: ../manage/users/index.rst:0
msgid "An inactive user displayed in a customer search list"
msgstr ""

#: ../manage/users/index.rst:145
msgid ""
"A slashed-out 👤 icon indicates an inactive user. In other cases, inactive "
"users are grayed out."
msgstr ""

#: ../manage/users/index.rst:151
msgid ""
"The :doc:`/manage/roles/index` define what users can do in the system. If "
"you need to grant someone privileges to edit the knowledge base or access "
"part of the admin panel, roles are the answer."
msgstr ""

#: ../manage/users/index.rst:156
msgid ""
"The :doc:`/manage/groups/access-levels` define which tickets an agent can "
"work with. If an agent is not receiving notifications for incoming tickets "
"or can't be assigned to a ticket, you should have a look on the group "
"permissions. Please note that the visibility of the group permission table "
"depends on the role selection. It only shows up, if the selected role has "
"the ``ticket.agent`` permission and when there is more than one active group "
"in the system."
msgstr ""

#: ../manage/users/index.rst:0
msgid "Permissions in the edit user dialog"
msgstr ""

#: ../manage/users/index.rst:171
msgid ""
"**Top:** User's roles decide what kind of actions they can perform and "
"which :doc:`groups </manage/groups/index>` they belong to. **Bottom:** Group "
"assignments can alternately be set on a per-user basis."
msgstr ""

#: ../manage/users/via-csv-import.rst:2
msgid "Managing Users via CSV Import"
msgstr ""

#: ../manage/users/via-csv-import.rst:8
msgid ""
"For persistent, automated user synchronization, consider integration with a "
"third-party directory system like :doc:`LDAP / Active Directory </system/"
"integrations/ldap/index>` or :doc:`Exchange </system/integrations/exchange>`."
msgstr ""

#: ../manage/users/via-csv-import.rst:20
msgid "Step 1: Inspect the Sample .csv"
msgstr ""

#: ../manage/users/via-csv-import.rst:22
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:27
msgid "Step 2: Export Your User Data to .csv"
msgstr ""

#: ../manage/users/via-csv-import.rst:32
msgid "the ``firstname`` and ``lastname`` attributes are **required**; and"
msgstr ""

#: ../manage/users/via-csv-import.rst:44
msgid ""
"If you have more than one value for a field, separate them with ``~~~`` as "
"above."
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-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/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. See :ref:"
"`user-details-reference` for help with the New/Edit User dialog."
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:13
msgid "👥 Creating and editing users"
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:0
msgid "Screencast showing a user being created."
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:12
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:24
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:44
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:31
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 ""
"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. To find your desired user, you have to narrow down your search."
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:41
msgid ""
"This limit is currently hard-coded and by design. We are aware of this "
"limitation and will probably change it sometime in the future."
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:55
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:51
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:85
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:62
msgid "Use the ⋮ **Actions** menu to 👁️ **View from user's perspective**."
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:64
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:69
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:72
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/users/via-the-admin-panel.rst:76
msgid "**⚠ With great power comes with great responsibility.**"
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:78
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 </manage/time-accounting>`) will "
"actually be performed from the user's account."
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:85
msgid "(On the other hand, if the user logs back in, you'll be booted, too.)"
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:96
msgid "🔑 Manage Two-Factor Authentication"
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:0
msgid "Screencast showing removal of user's two-factor method."
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:92
msgid ""
"Use the ⋮ **Actions** menu to remove a user's configured two-factor method."
msgstr ""

#: ../manage/users/via-the-admin-panel.rst:95
msgid ""
"It's possible to remove a single or all of the user's configured methods, if "
"they lose access. They can then set it up again by themselves via \"Avatar -"
"> Profile -> Password & Authentication\"."
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
msgid "How do Webhooks 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 "associated article(s)"
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 </manage/trigger>` or :doc:"
"`Scheduler </manage/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:53
msgid "Endpoint (mandatory)"
msgstr ""

#: ../manage/webhook/add.rst:48
msgid "Webhook endpoint Zammad sends its payload to."
msgstr ""

#: ../manage/webhook/add.rst:50
msgid ""
"Zammad ignores basic authentication parameters. See below how to configure :"
"ref:`username <HTTP Basic Authentication Username>` and :ref:`password <HTTP "
"Basic Authentication Password>` via separate fields."
msgstr ""

#: ../manage/webhook/add.rst:66
msgid "HMAC SHA1 Signature Token"
msgstr ""

#: ../manage/webhook/add.rst:56
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:59
msgid "**🔐 Security note**"
msgstr ""

#: ../manage/webhook/add.rst:61
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:65
msgid ""
"`Learn more about HUB-Signatures <https://www.w3.org/TR/websub/"
"#authenticated-content-distribution>`_"
msgstr ""

#: ../manage/webhook/add.rst:69
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:112
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:`/"
"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete."
msgstr ""

#: ../manage/webhook/add.rst:103
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:0
msgid "Custom payload code editor"
msgstr ""

#: ../manage/webhook/add.rst:111
msgid ""
"Pre-defined webhooks will always provide an initial custom payload, specific "
"for the associated service."
msgstr ""

#: ../manage/webhook/add.rst:115
msgid ""
"If required you can leave useful information for other Zammad admins to "
"understand the webhook in question better."
msgstr ""

#: ../manage/webhook/add.rst:119
msgid ""
"If set to ``inactive`` you can no longer select the webhook within trigger "
"or scheduler actions."
msgstr ""

#: ../manage/webhook/add.rst:122
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:114
#: ../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 </manage/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: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:62
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:73
#: ../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:75
#: ../manage/webhook/examples/rocket-chat-notifications.rst:50
#: ../manage/webhook/examples/slack-notifications.rst:69
msgid ""
"Go to :doc:`Webhook </manage/webhook/add>` 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:92
#: ../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:102
#: ../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:105
#: ../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 <generic-notifications-"
"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:111
#: ../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 <mattermost-removing-article-body>`. It will "
"also be :user-docs:`color coded </basics/service-ticket/settings/state."
"html#state-colors>` according to its latest state."
msgstr ""

#: ../manage/webhook/examples/mattermost-notifications.rst:117
msgid "Removing Article Content from the Mattermost Notification"
msgstr ""

#: ../manage/webhook/examples/mattermost-notifications.rst:119
#: ../manage/webhook/examples/microsoft-teams-notifications.rst:133
#: ../manage/webhook/examples/rocket-chat-notifications.rst:115
#: ../manage/webhook/examples/slack-notifications.rst:128
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:122
#: ../manage/webhook/examples/microsoft-teams-notifications.rst:136
#: ../manage/webhook/examples/rocket-chat-notifications.rst:118
#: ../manage/webhook/examples/slack-notifications.rst:131
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:125
#: ../manage/webhook/examples/microsoft-teams-notifications.rst:139
#: ../manage/webhook/examples/rocket-chat-notifications.rst:121
#: ../manage/webhook/examples/slack-notifications.rst:134
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:128
#: ../manage/webhook/examples/rocket-chat-notifications.rst:124
#: ../manage/webhook/examples/slack-notifications.rst:137
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:136
#: ../manage/webhook/examples/rocket-chat-notifications.rst:132
#: ../manage/webhook/examples/slack-notifications.rst:145
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:146
#: ../manage/webhook/examples/rocket-chat-notifications.rst:142
#: ../manage/webhook/examples/slack-notifications.rst:155
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:153
#: ../manage/webhook/examples/microsoft-teams-notifications.rst:158
#: ../manage/webhook/examples/rocket-chat-notifications.rst:149
#: ../manage/webhook/examples/slack-notifications.rst:162
msgid "Finally, click on **Submit** to save your webhook changes."
msgstr ""

#: ../manage/webhook/examples/mattermost-notifications.rst:155
#: ../manage/webhook/examples/microsoft-teams-notifications.rst:160
#: ../manage/webhook/examples/rocket-chat-notifications.rst:151
#: ../manage/webhook/examples/slack-notifications.rst:164
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:6
msgid ""
"Microsoft decided to retire `their Office 365 connectors <https://devblogs."
"microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-"
"microsoft-teams/>`_. The new way of connecting Microsoft Teams with third-"
"party tools is via `Workflows in Teams <https://support.microsoft.com/en-us/"
"office/browse-and-add-workflows-in-microsoft-teams-4998095c-8b72-4b0e-984c-"
"f2ad39e6ba9a>`_."
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-notifications.rst:11
msgid ""
"In the transitional period, we decided to keep this guide as is. Make sure "
"to follow Microsoft's guide as a replacement for **step 1** below, to "
"connect Teams and Zammad via Workflows."
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-notifications.rst:15
msgid ""
"If you already use this webhook and *didn't customize* the payload, the new "
"webhook is used automatically after updating Zammad. In this case, you just "
"need to create the workflow for your channel in Microsoft Teams. Otherwise "
"you have to manually adjust the payload in Zammad, too. See :doc:`Microsoft "
"Teams Payload </manage/webhook/examples/microsoft-teams-payload>` where you "
"can find the old and new defaults in case you need it."
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-notifications.rst:22
msgid ""
"To manage the connection in Zammad, you can go on with **step 2** on this "
"page."
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-notifications.rst:30
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:34
msgid "Step 1 - Setup Incoming Webhook Connector in your Teams Channel"
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-notifications.rst:36
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:43
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:50
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:54
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:60
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:70
msgid "Finally, close the connector configuration by clicking **Done**."
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-notifications.rst:84
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:94
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:107
msgid ""
"As a last step, you need to create a :doc:`Trigger <generic-notifications-"
"trigger>` for posting a notification to the Microsoft Teams channel under "
"certain conditions."
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-notifications.rst:116
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 <teams-removing-article-body>`. It will also "
"also be :user-docs:`color coded </basics/service-ticket/settings/state."
"html#state-colors>` according to its latest state."
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-notifications.rst:131
msgid "Removing Article Content from the Teams Notification"
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-notifications.rst:142
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:151
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/microsoft-teams-payload.rst:2
msgid "Microsoft Teams Webhook Payload"
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-payload.rst:4
msgid ""
"Microsoft is retiring their Office 365 connectors in favor of connecting "
"third-party tools via their Workflows. Because of that, the pre-defined "
"webhook in Zammad has changed. In case you need the old or new default "
"payload, you can find them below."
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-payload.rst:10
msgid "Payload for Office Connectors (old)"
msgstr ""

#: ../manage/webhook/examples/microsoft-teams-payload.rst:43
msgid "Payload for Workflows (new)"
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 <generic-notifications-"
"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 <rocket-chat-removing-article-body>`. "
"It will also be :user-docs:`color coded </basics/service-ticket/settings/"
"state.html#state-colors>` according to its latest state."
msgstr ""

#: ../manage/webhook/examples/rocket-chat-notifications.rst:113
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 <generic-notifications-"
"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 <slack-"
"removing-article-body>`. It will also be :user-docs:`color coded </basics/"
"service-ticket/settings/state.html#state-colors>` according to its latest "
"state."
msgstr ""

#: ../manage/webhook/examples/slack-notifications.rst:126
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:7
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:11
msgid "Direction"
msgstr ""

#: ../manage/webhook/log.rst:11
msgid "Always ``out``."
msgstr ""

#: ../manage/webhook/log.rst:14
msgid "The URL Zammad sent the request to."
msgstr ""

#: ../manage/webhook/log.rst:17
msgid "Method"
msgstr ""

#: ../manage/webhook/log.rst:17
msgid "Always ``POST``."
msgstr ""

#: ../manage/webhook/log.rst:21
msgid "Status"
msgstr ""

#: ../manage/webhook/log.rst:20
msgid ""
"Contains the HTTP status code the remote server replied with. Should be "
"``2xx`` if successful."
msgstr ""

#: ../manage/webhook/log.rst:24
msgid "Request"
msgstr ""

#: ../manage/webhook/log.rst:24
msgid "Contains the request Zammad sent (HTTP header and payload)"
msgstr ""

#: ../manage/webhook/log.rst:27
msgid "Response"
msgstr ""

#: ../manage/webhook/log.rst:27
msgid "Contains the remotes response header."
msgstr ""

#: ../manage/webhook/log.rst:30
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:337
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:341
msgid ""
"Webhooks will also include fields for any relevant :doc:`custom objects </"
"system/objects>` defined in your system."
msgstr ""

#: ../manage/webhook/payload.rst:344
msgid ""
"Attachments are *not included*; links to attachments *are* (authentication "
"required)."
msgstr ""

#: ../manage/webhook/payload.rst:347
msgid "Linked tickets are *not included*."
msgstr ""

#: ../manage/webhook/payload.rst:349
msgid "None of the following **user attributes** are included:"
msgstr ""

#: ../manage/webhook/payload.rst:351
msgid "``last_login``"
msgstr ""

#: ../manage/webhook/payload.rst:352
msgid "``login_failed``"
msgstr ""

#: ../manage/webhook/payload.rst:353
msgid "``password``"
msgstr ""

#: ../manage/webhook/payload.rst:354
msgid "``preferences``"
msgstr ""

#: ../manage/webhook/payload.rst:355
msgid "``group_ids``"
msgstr ""

#: ../manage/webhook/payload.rst:356
msgid "``groups``"
msgstr ""

#: ../manage/webhook/payload.rst:357
msgid "``authorization_ids``"
msgstr ""

#: ../manage/webhook/payload.rst:358
msgid "``authorizations``"
msgstr ""

#: ../manage/webhook/payload.rst:361
msgid "Pre-defined Webhooks"
msgstr ""

#: ../manage/webhook/payload.rst:363
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:37
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. In this case, the subject can "
"differ between title and email."
msgstr ""

#: ../misc/composer.rst:37
msgid ""
"If set to ``no``, Zammad will automatically use the tickets title as subject."
msgstr ""

#: ../misc/composer.rst:45
msgid "Email - full quote (default: ``no``)"
msgstr ""

#: ../misc/composer.rst:40
msgid ""
"Setting this option to ``yes`` will always add the content of the answered "
"article as quotation below your signature."
msgstr ""

#: ../misc/composer.rst:43
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:51
msgid "Email - quote header (default: ``yes``)"
msgstr ""

#: ../misc/composer.rst:48
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:51
msgid "Example: ``On Thursday, June 27, 2019, 3:37:11 PM, Jacob Smith wrote:``"
msgstr ""

#: ../misc/composer.rst:55
msgid "Twitter - tweet initials (default: ``yes``)"
msgstr ""

#: ../misc/composer.rst:54
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/first-steps.rst:4
msgid ""
"After the basic setup of Zammad with the getting started wizard, you will "
"see hints how to use the UI (see \"Intro\" below if you want to see them "
"again)."
msgstr ""

#: ../misc/first-steps.rst:7
msgid ""
"After these hints, the dashboard is presented to you which is basically the "
"Zammad start page. This dashboard provides some useful information for the "
"agents."
msgstr ""

#: ../misc/first-steps.rst:11
msgid ""
"You can switch to the \"First Steps\" section on top of the page to see "
"useful links for the start. Depending on your configuration and permission, "
"your list may look different."
msgstr ""

#: ../misc/first-steps.rst:None
msgid "Screenshot showing highlighted \"First Steps\" section"
msgstr ""

#: ../misc/first-steps.rst:23 ../settings/branding.rst:2
msgid "Branding"
msgstr ""

#: ../misc/first-steps.rst:23
msgid ""
"Link to the :doc:`branding section in the settings </settings/branding>`."
msgstr ""

#: ../misc/first-steps.rst:27
msgid "Your Email Configuration"
msgstr ""

#: ../misc/first-steps.rst:26
msgid ""
"Link to the :doc:`email channel section in the settings </channels/email/"
"index>`."
msgstr ""

#: ../misc/first-steps.rst:45
msgid "Invite agents/colleagues to help working on tickets"
msgstr ""

#: ../misc/first-steps.rst:32
msgid ""
"Here you can invite agents/colleagues to work with you in Zammad. It opens a "
"dialog in which you can provide details and assign a role."
msgstr ""

#: ../misc/first-steps.rst:0
msgid "Screenshot invite colleagues/agents dialog"
msgstr ""

#: ../misc/first-steps.rst:40
msgid ""
"Make sure to have configured the :doc:`roles and permission </manage/roles/"
"index>` according to your needs before inviting. To send the invitations via "
"email, you have to configure an :doc:`email notification channel </channels/"
"email/accounts/email-notification>` before too."
msgstr ""

#: ../misc/first-steps.rst:53
msgid "Invite customers to create issues in Zammad"
msgstr ""

#: ../misc/first-steps.rst:48
msgid ""
"Similar to the invitation of agents, you can invite customers to create "
"tickets/articles and to view them in the web UI. Of course, your customers "
"can create tickets anyway if they send you an email to a address which is "
"configured as an email channel. They even get an account created "
"automatically. For more information, a good starting point is the :doc:"
"`users section </manage/users/index>`."
msgstr ""

#: ../misc/first-steps.rst:56
msgid "How to Use it"
msgstr ""

#: ../misc/first-steps.rst:65
msgid "Intro"
msgstr ""

#: ../misc/first-steps.rst:59
msgid ""
"Here you can access the hints which you have seen after finishing the "
"getting started wizard. Click on \"Next\" to see all of them or click on the "
"X-button on the top right corner to close them."
msgstr ""

#: ../misc/first-steps.rst:0
msgid "Screenshot showing hint after finishing basic setup of Zammad"
msgstr ""

#: ../misc/first-steps.rst:69
msgid "Create Text Modules"
msgstr ""

#: ../misc/first-steps.rst:68
msgid ""
"Link to the :doc:`text module section in the settings </manage/text-"
"modules>`."
msgstr ""

#: ../misc/first-steps.rst:73
msgid "Create Macros"
msgstr ""

#: ../misc/first-steps.rst:72
msgid "Link to the :doc:`macro section in the settings </manage/macros>`."
msgstr ""

#: ../misc/first-steps.rst:76
msgid "Additional Channels"
msgstr ""

#: ../misc/first-steps.rst:80 ../settings/security/third-party/twitter.rst:2
msgid "Twitter"
msgstr ""

#: ../misc/first-steps.rst:79
msgid ""
"Link to the :doc:`Twitter channel in the settings </channels/twitter-x/"
"twitter>`."
msgstr ""

#: ../misc/first-steps.rst:83
msgid ""
"Link to the :doc:`Facebook channel in the settings </channels/facebook>`."
msgstr ""

#: ../misc/first-steps.rst:87
msgid "Link to the :doc:`chat channel in the settings </channels/chat>`."
msgstr ""

#: ../misc/first-steps.rst:91
msgid "Online Forms"
msgstr ""

#: ../misc/first-steps.rst:91
msgid "Link to the :doc:`form channel in the settings </channels/form>`."
msgstr ""

#: ../misc/object-conditions/basics.rst:2 ../misc/object-conditions/index.rst:2
msgid "Object Conditions"
msgstr ""

#: ../misc/object-conditions/basics.rst:7
msgid ""
"This page describes the attribute checks you can execute for different "
"object attributes. You can use these checks in different places in Zammad "
"like :doc:`triggers </manage/trigger>` or defining :doc:`overviews </manage/"
"overviews>`. Please note that the available attributes and the condition "
"operators depend on the object and where you want to use it."
msgstr ""

#: ../misc/object-conditions/basics.rst:13
msgid ""
"With these object attribute conditions you should be able to create quite "
"complex conditions. However, if you need to have additional AND/OR relations "
"for your conditions, have a look at the :doc:`expert conditions </misc/"
"object-conditions/expert-mode>` section, where you can find a description "
"how to use them."
msgstr ""

#: ../misc/object-conditions/basics.rst:20
msgid "Object Types"
msgstr ""

#: ../misc/object-conditions/basics.rst:22
msgid ""
"Depending on the location and selected attribute, the object context may "
"change. The default basic objects in Zammad are:"
msgstr ""

#: ../misc/object-conditions/basics.rst:28
#: ../misc/object-conditions/basics.rst:139
#: ../system/integrations/checkmk/admin-panel-reference.rst:15
msgid "Group"
msgstr ""

#: ../misc/object-conditions/basics.rst:30
msgid ""
"Within these 4 objects, you can even create your :doc:`own attributes </"
"system/objects>` and use them for conditions. However, there are more object "
"types and special context depending on the feature you want to create a "
"condition:"
msgstr ""

#: ../misc/object-conditions/basics.rst:35
#: ../misc/object-conditions/basics.rst:102
#: ../misc/object-conditions/basics.rst:166
#: ../misc/object-conditions/basics.rst:202
#: ../misc/object-conditions/basics.rst:208
#: ../misc/object-conditions/basics.rst:216
msgid "Article"
msgstr ""

#: ../misc/object-conditions/basics.rst:37
msgid "Execution time"
msgstr ""

#: ../misc/object-conditions/basics.rst:38
msgid "Session"
msgstr ""

#: ../misc/object-conditions/basics.rst:41
msgid "Attribute Types"
msgstr ""

#: ../misc/object-conditions/basics.rst:43
msgid ""
"Depending on the attribute type, you can choose from different operators to "
"execute checks and build your conditions."
msgstr ""

#: ../misc/object-conditions/basics.rst:46
msgid ""
"Have a look below where you can find a table with special functions which "
"you can see as some kind of attribute type and a a listing of attribute "
"types you can use in conditions in Zammad."
msgstr ""

#: ../misc/object-conditions/basics.rst:51
msgid "Special Fields"
msgstr ""

#: ../misc/object-conditions/basics.rst:53
msgid ""
"There are built in functions in Zammad which are selectable while creating "
"or editing a condition. Find them in the following table."
msgstr ""

#: ../misc/object-conditions/basics.rst:62
msgid "Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:65
msgid "Operators"
msgstr ""

#: ../misc/object-conditions/basics.rst:66
msgid "Offered values"
msgstr ""

#: ../misc/object-conditions/basics.rst:68
msgid "Article,"
msgstr ""

#: ../misc/object-conditions/basics.rst:70
msgid "ticket"
msgstr ""

#: ../misc/object-conditions/basics.rst:71
msgid "Checks performed action."
msgstr ""

#: ../misc/object-conditions/basics.rst:73
msgid "Only available in triggers."
msgstr ""

#: ../misc/object-conditions/basics.rst:74
#: ../misc/object-conditions/basics.rst:93
#: ../misc/object-conditions/basics.rst:104
#: ../misc/object-conditions/basics.rst:120
#: ../misc/object-conditions/basics.rst:135
#: ../misc/object-conditions/basics.rst:142
#: ../misc/object-conditions/basics.rst:152
#: ../misc/object-conditions/basics.rst:160
#: ../misc/object-conditions/basics.rst:168
#: ../misc/object-conditions/basics.rst:176
#: ../misc/object-conditions/basics.rst:186
#: ../misc/object-conditions/basics.rst:210
#: ../misc/object-conditions/basics.rst:220
#: ../system/core-workflows/condition-operators.rst:50
msgid "is"
msgstr ""

#: ../misc/object-conditions/basics.rst:75
#: ../misc/object-conditions/basics.rst:94
#: ../misc/object-conditions/basics.rst:105
#: ../misc/object-conditions/basics.rst:121
#: ../misc/object-conditions/basics.rst:136
#: ../misc/object-conditions/basics.rst:143
#: ../misc/object-conditions/basics.rst:153
#: ../misc/object-conditions/basics.rst:161
#: ../misc/object-conditions/basics.rst:169
#: ../misc/object-conditions/basics.rst:177
#: ../misc/object-conditions/basics.rst:187
#: ../misc/object-conditions/basics.rst:211
#: ../misc/object-conditions/basics.rst:221
#: ../system/core-workflows/condition-operators.rst:64
msgid "is not"
msgstr ""

#: ../misc/object-conditions/basics.rst:76
msgid "created"
msgstr ""

#: ../misc/object-conditions/basics.rst:77
msgid "updated"
msgstr ""

#: ../misc/object-conditions/basics.rst:78
msgid "merged into"
msgstr ""

#: ../misc/object-conditions/basics.rst:79
msgid "received merge"
msgstr ""

#: ../misc/object-conditions/basics.rst:81
msgid "Execution"
msgstr ""

#: ../misc/object-conditions/basics.rst:83
msgid "time"
msgstr ""

#: ../misc/object-conditions/basics.rst:84
msgid "Checks if event is in working time."
msgstr ""

#: ../misc/object-conditions/basics.rst:86
msgid "Only available in triggers and scheduler."
msgstr ""

#: ../misc/object-conditions/basics.rst:87
msgid "is in working time"
msgstr ""

#: ../misc/object-conditions/basics.rst:88
msgid "is not in working time"
msgstr ""

#: ../misc/object-conditions/basics.rst:89
msgid "Pre-defined calendars"
msgstr ""

#: ../misc/object-conditions/basics.rst:92
msgid "Checks ticket customer."
msgstr ""

#: ../misc/object-conditions/basics.rst:95
msgid "has changed"
msgstr ""

#: ../misc/object-conditions/basics.rst:97
#: ../misc/object-conditions/basics.rst:163
#: ../misc/object-conditions/basics.rst:189
msgid "specific user"
msgstr ""

#: ../misc/object-conditions/basics.rst:98
#: ../misc/object-conditions/basics.rst:156
#: ../misc/object-conditions/basics.rst:205
#: ../system/core-workflows/condition-operators.rst:78
msgid "not set"
msgstr ""

#: ../misc/object-conditions/basics.rst:99
msgid "Detected"
msgstr ""

#: ../misc/object-conditions/basics.rst:101
msgid "Language"
msgstr ""

#: ../misc/object-conditions/basics.rst:103
msgid "Checks the language of the article."
msgstr ""

#: ../misc/object-conditions/basics.rst:106
msgid "All languages which"
msgstr ""

#: ../misc/object-conditions/basics.rst:108
msgid "are supported by the"
msgstr ""

#: ../misc/object-conditions/basics.rst:110
msgid "language detection"
msgstr ""

#: ../misc/object-conditions/basics.rst:112
msgid "service."
msgstr ""

#: ../misc/object-conditions/basics.rst:113
#: ../misc/object-conditions/basics.rst:124
msgid "Existing"
msgstr ""

#: ../misc/object-conditions/basics.rst:115
msgid "members"
msgstr ""

#: ../misc/object-conditions/basics.rst:117
msgid "Checks if organization"
msgstr ""

#: ../misc/object-conditions/basics.rst:119
msgid "has members."
msgstr ""

#: ../misc/object-conditions/basics.rst:126
msgid "tickets"
msgstr ""

#: ../misc/object-conditions/basics.rst:129
msgid "customer/"
msgstr ""

#: ../misc/object-conditions/basics.rst:131
#: ../system/integrations/checkmk/api-reference.rst:138
#: ../system/integrations/checkmk/api-reference.rst:172
msgid "owner"
msgstr ""

#: ../misc/object-conditions/basics.rst:132
msgid "Checks if tickets are assigned."
msgstr ""

#: ../misc/object-conditions/basics.rst:134
msgid "Only available in scheduler."
msgstr ""

#: ../misc/object-conditions/basics.rst:141
msgid "Checks affected group."
msgstr ""

#: ../misc/object-conditions/basics.rst:144
msgid "All configured and"
msgstr ""

#: ../misc/object-conditions/basics.rst:146
msgid "active groups."
msgstr ""

#: ../misc/object-conditions/basics.rst:148
msgid "Ticket,"
msgstr ""

#: ../misc/object-conditions/basics.rst:150
#: ../system/integrations/checkmk/api-reference.rst:150
msgid "customer"
msgstr ""

#: ../misc/object-conditions/basics.rst:151
msgid "Checks affected organization."
msgstr ""

#: ../misc/object-conditions/basics.rst:154
msgid "current user organization"
msgstr ""

#: ../misc/object-conditions/basics.rst:155
msgid "specific organization"
msgstr ""

#: ../misc/object-conditions/basics.rst:159
msgid "Checks the owner."
msgstr ""

#: ../misc/object-conditions/basics.rst:164
#: ../misc/object-conditions/basics.rst:190
msgid "not set (not defined)"
msgstr ""

#: ../misc/object-conditions/basics.rst:165
msgid "Sender"
msgstr ""

#: ../misc/object-conditions/basics.rst:167
msgid "Checks the type of sender."
msgstr ""

#: ../misc/object-conditions/basics.rst:171
msgid "Agent"
msgstr ""

#: ../misc/object-conditions/basics.rst:175
msgid "Checks ticket state."
msgstr ""

#: ../misc/object-conditions/basics.rst:178
msgid "All configured"
msgstr ""

#: ../misc/object-conditions/basics.rst:180
msgid "ticket states."
msgstr ""

#: ../misc/object-conditions/basics.rst:181
msgid "Subscribe"
msgstr ""

#: ../misc/object-conditions/basics.rst:183
msgid "Checks if user is a"
msgstr ""

#: ../misc/object-conditions/basics.rst:185
msgid "ticket subscriber"
msgstr ""

#: ../misc/object-conditions/basics.rst:193
msgid "Checks tags of a ticket."
msgstr ""

#: ../misc/object-conditions/basics.rst:194
#: ../system/core-workflows/condition-operators.rst:32
msgid "contains all"
msgstr ""

#: ../misc/object-conditions/basics.rst:195
#: ../system/core-workflows/condition-operators.rst:38
msgid "contains one"
msgstr ""

#: ../misc/object-conditions/basics.rst:196
#: ../system/core-workflows/condition-operators.rst:34
msgid "contains all not"
msgstr ""

#: ../misc/object-conditions/basics.rst:197
#: ../system/core-workflows/condition-operators.rst:40
msgid "contains one not"
msgstr ""

#: ../misc/object-conditions/basics.rst:198
msgid "Text input field"
msgstr ""

#: ../misc/object-conditions/basics.rst:199
msgid "Time"
msgstr ""

#: ../misc/object-conditions/basics.rst:201
msgid "Accounting"
msgstr ""

#: ../misc/object-conditions/basics.rst:203
msgid "Checks if time is accounted."
msgstr ""

#: ../misc/object-conditions/basics.rst:204
#: ../system/core-workflows/condition-operators.rst:66
msgid "is set"
msgstr ""

#: ../misc/object-conditions/basics.rst:206
msgid "`-`"
msgstr ""

#: ../misc/object-conditions/basics.rst:209
msgid "Checks the type of the article."
msgstr ""

#: ../misc/object-conditions/basics.rst:212
msgid "All available"
msgstr ""

#: ../misc/object-conditions/basics.rst:214
msgid "article types."
msgstr ""

#: ../misc/object-conditions/basics.rst:215
msgid "Visibility"
msgstr ""

#: ../misc/object-conditions/basics.rst:217
msgid "Checks the visibility"
msgstr ""

#: ../misc/object-conditions/basics.rst:219
msgid "of the article."
msgstr ""

#: ../misc/object-conditions/basics.rst:222
msgid "internal"
msgstr ""

#: ../misc/object-conditions/basics.rst:223
msgid "public"
msgstr ""

#: ../misc/object-conditions/basics.rst:226
msgid "Text Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:228
msgid ""
"Checks if any field of type text contains a specific string. The configured "
"\"Type\" of input fields has no impact on the available options."
msgstr ""

#: ../misc/object-conditions/basics.rst:231
#: ../misc/object-conditions/basics.rst:255
#: ../misc/object-conditions/basics.rst:266
#: ../misc/object-conditions/basics.rst:277
#: ../misc/object-conditions/basics.rst:290
#: ../misc/object-conditions/basics.rst:331
#: ../misc/object-conditions/basics.rst:378
#: ../misc/object-conditions/basics.rst:389
#: ../misc/object-conditions/basics.rst:407
#: ../misc/object-conditions/basics.rst:418
msgid "Available operators for matching:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**contains**: Matches if text contains a specific string."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**contains not**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Matches if text does not contain a specific string."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**is any of**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Matches if text is equal to any of given tokens."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**is none of**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Matches if text is not equal to all of given tokens."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**starts with one of**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Matches if text starts with one of given tokens."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**ends with one of**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Matches if text ends with one of given tokens."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**matches regex**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid ""
"Evaluates if text matches provided regular expression (see also :ref:"
"`remarks <regex>`)."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**does not match regex**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Evaluates if text does not match provided regular expression."
msgstr ""

#: ../misc/object-conditions/basics.rst:251
msgid "Textarea Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:253
msgid "Checks if any field of type textarea contains a specific string."
msgstr ""

#: ../misc/object-conditions/basics.rst:257
msgid "**contains**"
msgstr ""

#: ../misc/object-conditions/basics.rst:258
msgid "**contains not**"
msgstr ""

#: ../misc/object-conditions/basics.rst:259
#: ../misc/object-conditions/basics.rst:270
#: ../misc/object-conditions/basics.rst:281
#: ../misc/object-conditions/basics.rst:382
#: ../misc/object-conditions/basics.rst:411
msgid "**has changed**"
msgstr ""

#: ../misc/object-conditions/basics.rst:262
msgid "Boolean Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:264
msgid "Checks if any field of type boolean is true."
msgstr ""

#: ../misc/object-conditions/basics.rst:268
#: ../misc/object-conditions/basics.rst:279
#: ../misc/object-conditions/basics.rst:380
#: ../misc/object-conditions/basics.rst:409
msgid "**is**"
msgstr ""

#: ../misc/object-conditions/basics.rst:269
#: ../misc/object-conditions/basics.rst:280
#: ../misc/object-conditions/basics.rst:381
#: ../misc/object-conditions/basics.rst:410
msgid "**is not**"
msgstr ""

#: ../misc/object-conditions/basics.rst:273
msgid "Integer Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:275
msgid "Checks if any field of type integer has a specific value."
msgstr ""

#: ../misc/object-conditions/basics.rst:284
msgid "Date Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:286
msgid ""
"Checks if a date is before or past (both absolute or relativ) a specific "
"point in time or time period. Relative operators allow you to define a time "
"period in seconds, minutes, hours, days, weeks, months or years."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**before (absolute)**:"
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 "**after (absolute)**:"
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 "**before (relative)**:"
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 "**after (relative)**:"
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 "**within last (relative)**:"
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 "**within next (relative)**:"
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 "**till (relative)**:"
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 "**from (relative)**:"
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 "**has changed**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "The field has been changed during a ticket update."
msgstr ""

#: ../misc/object-conditions/basics.rst:319
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:325
msgid "Date & Time Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:327
msgid ""
"Checks if a date and time is before or past (both absolute or relativ) a "
"specific point in time or time period. Relative operators allow you to "
"define a time period in seconds, minutes, hours, days, weeks, months or "
"years."
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 "**has reached**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Checks if the time set in this field was reached."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid ""
"Only available for Pending time and Escalation time in Trigger conditions."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**has reached warning**:"
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:0
msgid "Only available for Ticket's Escalation time in Trigger conditions."
msgstr ""

#: ../misc/object-conditions/basics.rst:368
msgid ""
"Have a look at the diagram above. It applies also for date & time but you "
"additionally have hours and minutes on top to use."
msgstr ""

#: ../misc/object-conditions/basics.rst:372
msgid "Single Selection Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:374
msgid ""
"Checks if selected field values match the attribute value. It 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:385
msgid "Multiple Selection Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:387
msgid "Checks if selected field values match the attribute value(s)."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**contains all**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Matches if all given field values are selected."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**contains one**:"
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 "**contains all not**:"
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 "**contains one not**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Matches if one specific given field value is not selected."
msgstr ""

#: ../misc/object-conditions/basics.rst:402
msgid "Single Tree Selection Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:404
msgid ""
"Checks if a selected field value match the attribute value. Selecting more "
"than one value in the condition will act like an \"OR\" clause."
msgstr ""

#: ../misc/object-conditions/basics.rst:414
msgid "Multiple Tree Selection Field"
msgstr ""

#: ../misc/object-conditions/basics.rst:416
msgid "Checks if selected field value(s) match the attribute value(s)."
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**contains all**"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**contains one**"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**contains all not**"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "**contains one not**"
msgstr ""

#: ../misc/object-conditions/basics.rst:430
msgid "Additional Information and Remarks"
msgstr ""

#: ../misc/object-conditions/basics.rst:439
msgid "Ticket context conditions do not support:"
msgstr ""

#: ../misc/object-conditions/basics.rst:436
msgid "regular expressions"
msgstr ""

#: ../misc/object-conditions/basics.rst:437
msgid "case sensitive string conditions"
msgstr ""

#: ../misc/object-conditions/basics.rst:438
msgid ""
"Basic conditions do not support the same attribute to be selected more than "
"once"
msgstr ""

#: ../misc/object-conditions/basics.rst:447
msgid "*has changed* conditions:"
msgstr ""

#: ../misc/object-conditions/basics.rst:442
msgid "Are only available for ticket attributes and don't affect:"
msgstr ""

#: ../misc/object-conditions/basics.rst:444
msgid "Ticket articles attributes"
msgstr ""

#: ../misc/object-conditions/basics.rst:445
msgid "Organization attributes"
msgstr ""

#: ../misc/object-conditions/basics.rst:446
msgid "User attributes"
msgstr ""

#: ../misc/object-conditions/basics.rst:447
msgid "Group attributes"
msgstr ""

#: ../misc/object-conditions/basics.rst:460
msgid "Differences in input fields:"
msgstr ""

#: ../misc/object-conditions/basics.rst:450
msgid ""
"Please note that the input field for tokens doesn't support the comma as "
"separator (as in the input field for tags). If you use the comma in the "
"token input field, the comma is included in you token."
msgstr ""

#: ../misc/object-conditions/basics.rst:454
msgid "**Example**:"
msgstr ""

#: ../misc/object-conditions/basics.rst:0
msgid "Example of comma usage in token input field"
msgstr ""

#: ../misc/object-conditions/basics.rst:459
msgid ""
"``A`` added with enter/tab, ``B`` and ``C`` separated with comma (resulting "
"in one token)."
msgstr ""

#: ../misc/object-conditions/basics.rst:465
msgid "Regex"
msgstr ""

#: ../misc/object-conditions/basics.rst:470
msgid "Regex support"
msgstr ""

#: ../misc/object-conditions/basics.rst:468
msgid ""
"*matches regex* and *does not match regex* are supported only in Triggers, "
"Time Accounting selector, Postmaster Filters, Automatic ticket assignment "
"and Core Workflow."
msgstr ""

#: ../misc/object-conditions/basics.rst:475
msgid "\"Old\" style ``regex:...`` conditions"
msgstr ""

#: ../misc/object-conditions/basics.rst:473
msgid ""
"If you update your Zammad from 6.0 or prior and you have already conditions "
"with *contains* or *contains not* including a regex filter (i.e. ``regex:"
"^(foo|bar)$``), Zammad tries to migrate them to the new *matches regex* and "
"*does not match regex* operators."
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:2
msgid "Expert Mode"
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. This section "
"expects that you had a look at :doc:`basics` already."
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:15
msgid "Limitation"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:17
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:21
msgid "Switching to Expert Mode"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:23
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:31
msgid "Logic Block Conditions"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:33
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:40
msgid "Match all (AND)"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:39
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:44
msgid "Match any (OR)"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:43
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:48
msgid "Match none (NOT)"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:47
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:50
msgid ""
"See :ref:`evaluation order <evaluation-order>` to understand how Zammad "
"evaluates triggers in expert mode."
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:54
msgid "Adding Conditions and Logic Blocks"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:56
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:78
msgid "Icon for adding a new subclause block"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:59
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:67
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:75
msgid ""
"Note that removing condition blocks removes **all blocks and conditions** "
"with it!"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:83
msgid "Re-arranging Conditions and Logic Blocks"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:85
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:88
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:91
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:100
msgid "Evaluation Order"
msgstr ""

#: ../misc/object-conditions/expert-mode.rst:102
msgid ""
"Here's a fairly complex diagram on how Zammad evaluates conditions and their "
"blocks."
msgstr ""

#: ../misc/object-conditions/index.rst:4
msgid ""
"In many places in Zammad you can use conditions based on attribute checks to "
"filter tickets and perform actions."
msgstr ""

#: ../misc/object-conditions/index.rst:7
msgid ""
"Please note that the availability of the different attributes and special "
"fields depend on the feature you are using and the object context."
msgstr ""

#: ../misc/object-conditions/index.rst:10
msgid "This guide is split into two sections:"
msgstr ""

#: ../misc/object-conditions/index.rst:13
msgid ":doc:`/misc/object-conditions/basics`"
msgstr ""

#: ../misc/object-conditions/index.rst:13
msgid "Learn how Zammad's conditions work to adapt to your environment."
msgstr ""

#: ../misc/object-conditions/index.rst:17
msgid ":doc:`/misc/object-conditions/expert-mode`"
msgstr ""

#: ../misc/object-conditions/index.rst:16
msgid ""
"Learn how Zammad's expert mode for conditions allows you to create even more "
"powerful conditions with AND/OR relations."
msgstr ""

#: ../misc/variables.rst:2
msgid "Variables"
msgstr ""

#: ../misc/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 <https://community.zammad."
"org>`_."
msgstr ""

#: ../misc/variables.rst:10
msgid ""
"Variables can be called by typing ``::`` (just like text modules in the "
"frontend), as long as you're in a supported text field within the backend. "
"Zammad will display all variables being available within this context and "
"replace it to the variable as soon as you selected an entry."
msgstr ""

#: ../misc/variables.rst:15
msgid ""
"You have an empty field which you referenced and it appears as ``-``? That's "
"currently working as designed - you might want to ensure that these fields "
"always have a value."
msgstr ""

#: ../misc/variables.rst:20
msgid "Variable Categories"
msgstr ""

#: ../misc/variables.rst:31
msgid "Wait, What About Custom Objects?"
msgstr ""

#: ../misc/variables.rst:33
msgid ""
"Good point! Of course, we can't predict what objects you might create, but "
"we can give you a hint on how to put the puzzle together to get your custom "
"values."
msgstr ""

#: ../misc/variables.rst:36
msgid ""
"For this, we'll talk about the inner part of the variable (so everything "
"within ``#{}``), please put the outer part around to have a valid variable. "
"The first part of the variable name consist of the object type. Currently "
"these are:"
msgstr ""

#: ../misc/variables.rst:41
msgid "Ticket (``ticket``)"
msgstr ""

#: ../misc/variables.rst:42
msgid "User (``user``)"
msgstr ""

#: ../misc/variables.rst:43
msgid "Organization (``organization``)"
msgstr ""

#: ../misc/variables.rst:44
msgid "Group (``group``)"
msgstr ""

#: ../misc/variables.rst:46
msgid ""
"The second part is the name of the attribute. This is the name you define "
"during object creation and can be found within the object attribute menu at "
"any time. The first and second part of a variable is divided by a point, e."
"g.: ``ticket.number`` which will in total be ``#{ticket.number}``."
msgstr ""

#: ../misc/variables.rst:51
msgid ""
"Now, in some situations it's possible that you'll need to use a third part. "
"The best example for such a situation would be a ``select`` or ``tree-"
"select`` field which will by default return the key value, not it's display "
"name. For this, just extend your variable with ``.value``. This will result "
"in ``#{ticket.select.value}``."
msgstr ""

#: ../misc/variables.rst:60
msgid "Using Translated Variables"
msgstr ""

#: ../misc/variables.rst:62
msgid ""
"If you want to use a translated variable in triggers or schedulers, you can "
"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` "
"tells Zammad to search for fitting translated strings. The used output "
"language is based on the system language of Zammad which you can set in the "
"admin panel under :doc:`/settings/branding` or based on the selected locale "
"in the trigger/scheduler edit dialog."
msgstr ""

#: ../misc/variables.rst:69
msgid ""
"A possible use-case: you want to send your customers updates on tickets via "
"trigger or scheduler which should include the state of the ticket. Using the "
"default ``#{ticket.state.name}`` (without the translation flag ``t()``) "
"would lead to the output of the original (english) name of the state."
msgstr ""

#: ../misc/variables.rst:75
msgid "Date and Time Formatting"
msgstr ""

#: ../misc/variables.rst:77
msgid ""
"The system (trigger/scheduler selected) locale and timezone predefines a "
"default format of date and timestamp. This format is customizable by using "
"the ``dt()`` method."
msgstr ""

#: ../misc/variables.rst:79
msgid "The method arguments are as follows:"
msgstr ""

#: ../misc/variables.rst:81
msgid "The date or timestamp variable you want to format."
msgstr ""

#: ../misc/variables.rst:82
msgid "The output format string."
msgstr ""

#: ../misc/variables.rst:83
msgid "The timezone to apply (optional)."
msgstr ""

#: ../misc/variables.rst:85
#: ../system/objects/external-data-source-example.rst:23
msgid "**Example:**"
msgstr ""

#: ../misc/variables.rst:86
msgid ""
"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/"
"Berlin\")}``"
msgstr ""

#: ../misc/variables.rst:87
msgid "Monday, 2024-03-18 15:31 in the office"
msgstr ""

#: ../misc/variables.rst:89
msgid ""
"If you want to use our example, make sure to paste the string above without "
"formatting (``CTRL+Shift+v``), otherwise it won't work."
msgstr ""

#: ../misc/variables.rst:93
msgid "The following table lists available format directives:"
msgstr ""

#: ../misc/variables.rst:99
msgid "Parameter"
msgstr ""

#: ../misc/variables.rst:102
msgid "``%Y``"
msgstr ""

#: ../misc/variables.rst:103
msgid "Year with 4 digits"
msgstr ""

#: ../misc/variables.rst:104
msgid "Use ``%y`` for year with 2 digits"
msgstr ""

#: ../misc/variables.rst:105
msgid "``%m``"
msgstr ""

#: ../misc/variables.rst:106
msgid "Month of year (as number with zero-padding)"
msgstr ""

#: ../misc/variables.rst:107
msgid "Use ``%-m`` for month without zero-padding"
msgstr ""

#: ../misc/variables.rst:108
msgid "``%d``"
msgstr ""

#: ../misc/variables.rst:109
msgid "Day of month (as number with zero-padding)"
msgstr ""

#: ../misc/variables.rst:110
msgid "Use ``%e`` for day without zero-padding"
msgstr ""

#: ../misc/variables.rst:111
msgid "``%H``"
msgstr ""

#: ../misc/variables.rst:112
msgid "Hour of day in 24h notation with zero-padding"
msgstr ""

#: ../misc/variables.rst:113
msgid "Use ``%k`` for hour without zero-padding"
msgstr ""

#: ../misc/variables.rst:114
msgid "``%I``"
msgstr ""

#: ../misc/variables.rst:115
msgid "Hour of day in 12h notation with zero-padding"
msgstr ""

#: ../misc/variables.rst:116
msgid ""
"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian "
"indicator"
msgstr ""

#: ../misc/variables.rst:117
msgid "``%M``"
msgstr ""

#: ../misc/variables.rst:118
msgid "Minute of hour"
msgstr ""

#: ../misc/variables.rst:120
msgid "``%S``"
msgstr ""

#: ../misc/variables.rst:121
msgid "Second of Minute"
msgstr ""

#: ../misc/variables.rst:123
msgid "``%A``"
msgstr ""

#: ../misc/variables.rst:124
msgid "Weekday name"
msgstr ""

#: ../misc/variables.rst:125
msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name"
msgstr ""

#: ../misc/variables.rst:126
msgid "``%B``"
msgstr ""

#: ../misc/variables.rst:127
msgid "Month name"
msgstr ""

#: ../misc/variables.rst:128
msgid "Use ``%b`` for abbreviated name"
msgstr ""

#: ../misc/variables.rst:129
msgid "``%U``"
msgstr ""

#: ../misc/variables.rst:130
msgid "Week number of current year"
msgstr ""

#: ../misc/variables.rst:131
msgid "Use ``%W`` for a different calculation method"
msgstr ""

#: ../misc/variables.rst:134
msgid ""
"We support the known format directives for the Ruby built-in method "
"``strftime`` of the ``DateTime`` class. For more information, see `here "
"<https://apidock.com/ruby/DateTime/strftime>`_."
msgstr ""

#: ../misc/variables/article.rst:2
msgid "Articles"
msgstr ""

#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4
#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4
msgid ""
"If you're missing variables or are not sure if something is not working as "
"expected, feel free to ask over at the `Community <https://community.zammad."
"org>`_."
msgstr ""

#: ../misc/variables/article.rst:6
msgid ""
"Below you can find all available ticket article-based variables within "
"Zammad. These can be called via triggers for example. If you're unsure if "
"Zammad does support variables at the point you're at, you can try to type "
"``::`` to check."
msgstr ""

#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9
#: ../misc/variables/ticket.rst:9
msgid ""
"The below list gives you an example what kind of data you can expect, it's "
"not intended to explain the data itself."
msgstr ""

#: ../misc/variables/article.rst:11
msgid "Article Variables"
msgstr ""

#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1
#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "name"
msgstr ""

#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1
#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "variable"
msgstr ""

#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1
#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "example"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Cc"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.cc}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``jdoe@example.com, company@example.com``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Address"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.address}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Department"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.department}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``Sales`` or empty if not set in user object"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Email"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.email}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``jdoe@example.com``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Fax"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.fax}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``+4930123456789`` or empty if not set in user object"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Firstname"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.firstname}``"
msgstr ""

#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1
msgid "``Joe`` or empty if not set"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Lastname"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.lastname}``"
msgstr ""

#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1
#: ../misc/variables/ticket.rst:1
msgid "``Doe`` or empty if not set"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Login"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.login}``"
msgstr ""

#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1
#: ../misc/variables/ticket.rst:1
msgid "``jdoe``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Mobile"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.mobile}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Note"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.note}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``Some note about user`` or empty if not set in user object"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Phone"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.phone}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > VIP"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.vip}``"
msgstr ""

#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1
msgid "``true`` or ``false``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created by > Web"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_by.web}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``https://zammad.com`` or empty if not set in user object"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Created"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.created_at}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``2019-10-08 15:24:47 UTC``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > From"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.from}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid ""
"``Joe Doe <jdoe@example.com>`` may differ, depends on ``FROM`` of send mail"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Sender > Name"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.sender.name}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``Customer``, ``Agent`` or ``System``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Subject"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.subject}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``My amazing subject``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Text"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.body}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``Test`` without formatting (plain)"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > TicketID"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.ticket_id}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``1`` (not ticket number)"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > To"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.to}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``helpdesk@example.com``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Type > Name"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.type.name}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid ""
"``email`` (`list of article types <https://github.com/zammad/zammad/blob/"
"develop/db/seeds/ticket_article_types.rb>`_)"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Address"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.address}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Department"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.department}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Email"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.email}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Fax"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.fax}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Firstname"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.firstname}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Lastname"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.lastname}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Login"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.login}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Mobile"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.mobile}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Note"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.note}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Phone"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.phone}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > VIP"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.vip}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated by > Web"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_by.web}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Updated"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.updated_at}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article > Visibility"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.internal}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``false`` or ``true`` (false if not internal)"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "Article Text as HTML (not referenced)"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``#{article.body_as_html}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``Test`` with formatting"
msgstr ""

#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1
msgid "Ticket > Article#"
msgstr ""

#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1
msgid "``#{ticket.article_count}``"
msgstr ""

#: ../misc/variables/article.rst:1
msgid "``1`` number of ticket articles"
msgstr ""

#: ../misc/variables/config.rst:2
msgid "Config"
msgstr ""

#: ../misc/variables/config.rst:6
msgid ""
"Below you'll find config related variables. These hold useful configuration "
"information that you can use within e.g. triggers to show necessary "
"information to your customer."
msgstr ""

#: ../misc/variables/config.rst:11
msgid "Config Variables"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "Config > Fully Qualified Domain Name"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``#{config.fqdn}``"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``zammad.example.com``"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "Config > HTTP type"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``#{config.http_type}``"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``https`` or ``http``"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "Config > Organization"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``#{config.organization}``"
msgstr ""

#: ../misc/variables/config.rst:1
msgid ""
"``Zammad GmbH`` value set in `Branding <https://admin-docs.zammad.org/en/"
"latest/settings-branding.html>`_"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "Config > Product Name"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``#{config.product_name}``"
msgstr ""

#: ../misc/variables/config.rst:1
msgid ""
"``Helpdesk`` value set in `Branding <https://admin-docs.zammad.org/en/latest/"
"settings-branding.html>`_"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "Config > SystemID"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``#{config.system_id}``"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``31`` (value between 1 and 99)"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "Config > Ticket Hook"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``#{config.ticket_hook}``"
msgstr ""

#: ../misc/variables/config.rst:1
msgid "``Ticket#``"
msgstr ""

#: ../misc/variables/current-user.rst:2
msgid "Current User"
msgstr ""

#: ../misc/variables/current-user.rst:6
msgid ""
"Current user variables always return values of the current user that caused "
"e.g. a trigger to run."
msgstr ""

#: ../misc/variables/current-user.rst:8
msgid ""
"Due to the above fact, these variables are often not (yet) set or available "
"for usage."
msgstr ""

#: ../misc/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 ""

#: ../misc/variables/current-user.rst:13
msgid "Current User Variables"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Address"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.address}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``Some street 1, 12345 Berlin`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Avatar"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.avatar(60,60)}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "avatar picture with width and height in pixel (e.g. 60,60)"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created at"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_at}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``2019-10-07 16:25:00 UTC``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Address"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.address}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Avatar"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.avatar(60,60)}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Department"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.department}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``Sales`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Email"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.email}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``jdoe@customer.tld``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Fax"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.fax}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``004930123464789`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Firstname"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.firstname}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``John`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Lastname"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.lastname}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Login"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.login}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Mobile"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.mobile}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``0049176123456789`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Note"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.note}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``Some note to this user`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Phone"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.phone}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``004930123456789`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > VIP"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.vip}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Created by > Web"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.created_by.web}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``https://zammad.org`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Department"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.department}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Email"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.email}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Fax"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.fax}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Firstname"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.firstname}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Lastname"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.lastname}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Login"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.login}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Mobile"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.mobile}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Note"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.note}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Organization > Domain based assignment"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.organization.domain_assignment}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Organization > Domain"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.organization.domain}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``zammad.com`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Organization > Name"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.organization.name}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``Zammad GmbH``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Organization > Note"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.organization.note}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``A note to the organization of the user`` or empty if not set"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Organization > Shared organization"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.organization.shared}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Organization > VIP"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.organization.vip}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Phone"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.phone}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated at"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_at}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Address"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.address}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Avatar"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.avatar(60,60)}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Department"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.department}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Email"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.email}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Fax"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.fax}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Firstname"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.firstname}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Lastname"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.lastname}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Login"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.login}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Mobile"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.mobile}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Note"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.note}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Phone"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.phone}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > VIP"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.vip}``"
msgstr ""

#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1
msgid "``false`` or ``true``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Updated by > Web"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.updated_by.web}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > VIP"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.vip}``"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "Current User > Web"
msgstr ""

#: ../misc/variables/current-user.rst:1
msgid "``#{user.web}``"
msgstr ""

#: ../misc/variables/ticket.rst:6
msgid ""
"Below you can find all available ticket-based variables within Zammad. These "
"can be called via triggers for example. If you're unsure if Zammad does "
"support variables at the point you're at, you can try to type ``::`` to "
"check."
msgstr ""

#: ../misc/variables/ticket.rst:12
msgid "Ticket Variables"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Accounted Time"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.time_unit}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``1``, ``2.75`` or empty response"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``3``, any number of articles existing in the ticket right now"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Closing time"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.close_at}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "2019-10-07 17:25:00 UTC"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created at"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_at}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "2019-10-07 16:25:00 UTC"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Address"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.address}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Avatar"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.avatar(60,60)}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Department"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.department}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Email"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.email}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Fax"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.fax}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Firstname"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.firstname}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Lastname"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.lastname}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Login"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.login}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Mobile"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.mobile}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Note"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.note}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Phone"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.phone}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > VIP"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.vip}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Created by > Web"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.created_by.web}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Address"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.address}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Avatar"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.avatar(60,60)}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Department"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.department}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Email"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.email}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Fax"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.fax}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Firstname"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.firstname}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Lastname"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.lastname}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Login"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.login}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Mobile"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.mobile}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Note"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.note}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Phone"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.phone}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > VIP"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.vip}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Customer > Web"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.customer.web}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Escalation at"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.escalation_at}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > First response"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.first_response_at}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Group > Assign Follow-Ups"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.group.follow_up_assignment}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Group > Assignment Timeout"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.group.assignment_timeout}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``20`` or empty if not configured"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Group > Follow-up possible"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.group.follow_up_possible}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``no`` or ``yes``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Group > Name"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.group.name}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``Sales``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Group > Note"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.group.note}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``Note about this group``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > ID"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.id}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``17``, ``5281``, ..."
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Last contact (agent)"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.last_contact_agent_at}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Last contact (customer)"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.last_contact_customer_at}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid ""
"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note "
"`Ticket last contact behavior Settings <https://admin-docs.zammad.org/en/"
"latest/settings-ticket.html>`_ for this)"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Last contact"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.last_contact_at}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Number"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.number}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``31001``, ``201910731001``, ..."
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Organization > Domain based assignment"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.organization.domain_assignment}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Organization > Domain"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.organization.domain}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``domain.tld`` or empty if not set"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Organization > Name"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.organization.name}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``Zammad GmbH`` or empty if not set"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Organization > Note"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.organization.note}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Organization > Shared organization"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.organization.shared}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Organization > VIP"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.organization.vip}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Address"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.address}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Avatar"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.avatar(60,60)}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Department"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.department}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``Support`` or empty if not set"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Email"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.email}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``agent@company.tld`` or empty if not set"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Fax"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.fax}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Firstname"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.firstname}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``Max`` or empty if not set"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Lastname"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.lastname}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``Mustermann`` or empty if not set"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Login"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.login}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``agent``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Mobile"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.mobile}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Note"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.note}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Phone"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.phone}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > VIP"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.vip}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Owner > Web"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.owner.web}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``https://zammad.com`` or empty if not set"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Pending till"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.pending_time}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``2019-10-07 16:25:00 UTC`` or empty if not set"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Priority > Name"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.priority.name}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``2 normal``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > State > Name"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.state.name}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``new``, ``open``, ..."
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Tags"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.tags}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid ""
"Currently not available, see `Issue 2769 <https://github.com/zammad/zammad/"
"issues/2769>`_"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Title"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.title}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid ""
"``My amazing Subject`` (normally subject, can be edited within Interface and "
"thus differ)"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated at"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_at}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Address"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.address}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Avatar"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.avatar(60,60)}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Department"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.department}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Email"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.email}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Fax"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.fax}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Firstname"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.firstname}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Lastname"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.lastname}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Login"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.login}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Mobile"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.mobile}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Note"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.note}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Phone"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.phone}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > VIP"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.vip}``"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "Ticket > Updated by > Web"
msgstr ""

#: ../misc/variables/ticket.rst:1
msgid "``#{ticket.updated_by.web}``"
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:19
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:18
msgid ""
"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your "
"change will not be saved."
msgstr ""

#: ../settings/branding.rst:22
msgid ""
"Allows to set the default language of the Zammad instance. The here defined "
"locale mostly acts as a fallback for:"
msgstr ""

#: ../settings/branding.rst:25
msgid "user preferences (if Zammad can't detect the users locale)"
msgstr ""

#: ../settings/branding.rst:26
msgid "CSV output (reporting, time accounting)"
msgstr ""

#: ../settings/branding.rst:30
msgid "Define the timezone of your Zammad installation."
msgstr ""

#: ../settings/branding.rst:32
msgid ""
"This does not have any effect on timings for your agents or how Zammad "
"stores date and time values."
msgstr ""

#: ../settings/branding.rst:35
msgid "Changing this value has direct consequences on the following areas:"
msgstr ""

#: ../settings/branding.rst:37
msgid ":doc:`/manage/scheduler` tasks"
msgstr ""

#: ../settings/branding.rst:38
msgid "search indexing (and thus reporting)"
msgstr ""

#: ../settings/branding.rst:40
msgid "calendar subscriptions"
msgstr ""

#: ../settings/branding.rst:41
msgid "browser printing"
msgstr ""

#: ../settings/branding.rst:43
msgid ""
"Please note that some of above are fallbacks in case Zammad could not detect "
"the agents timezone correctly."
msgstr ""

#: ../settings/branding.rst:77
msgid "Pretty Date"
msgstr ""

#: ../settings/branding.rst:47
msgid ""
"This setting allows you to define how Zammad should display time stamps "
"within the interface to all users."
msgstr ""

#: ../settings/branding.rst:50
msgid ""
"This does not have any effect on how Zammad returns e.g. time values via "
"variables."
msgstr ""

#: ../settings/branding.rst:77
msgid "Choose in between the following options:"
msgstr ""

#: ../settings/branding.rst:64
msgid "relative"
msgstr ""

#: ../settings/branding.rst:55
msgid ""
"This timestamp shows a relative time span until it switches to a date. Over "
"time, it will change as follows:"
msgstr ""

#: ../settings/branding.rst:58
msgid "just now"
msgstr ""

#: ../settings/branding.rst:59
msgid "5 minutes ago"
msgstr ""

#: ../settings/branding.rst:60
msgid "3 days 1 hour ago"
msgstr ""

#: ../settings/branding.rst:61
msgid "``03/04/2022``"
msgstr ""

#: ../settings/branding.rst:63
msgid "Hovering the timestamp helps, you'll always get a clean timestamp then."
msgstr ""

#: ../settings/branding.rst:71
msgid "absolute"
msgstr ""

#: ../settings/branding.rst:67
msgid ""
"This timestamp always includes the week day. For one week after creation, "
"the timestamp will not contain the date itself: Thursday 18:35."
msgstr ""

#: ../settings/branding.rst:71
msgid "After a week it will switch to: ``Friday 4. Mar 16:00``."
msgstr ""

#: ../settings/branding.rst:76
msgid "timestamp"
msgstr ""

#: ../settings/branding.rst:74
msgid ""
"This will cause Zammad to show a complete timestamp according to your locale "
"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for "
"German e.g. ``12.03.2022 14:40``."
msgstr ""

#: ../settings/branding.rst:78
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:8
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:38
#: ../settings/security/base.rst:66
msgid "Default setting: ``yes``"
msgstr ""

#: ../settings/security/base.rst:0
msgid "Figure showing activated \"New User Accounts\" setting"
msgstr ""

#: ../settings/security/base.rst:22
msgid ""
"Deactivation of above function **does not** deactivate automatic account "
"creation! This means: If a user writes e.g. an email to Zammad and has no "
"account yet, Zammad will automatically create the account. User accounts are "
"a direct dependency of tickets and thus technically mandatory."
msgstr ""

#: ../settings/security/base.rst:29
msgid "Lost Password"
msgstr ""

#: ../settings/security/base.rst:33
msgid ""
"Activates the `lost password` function on the login page. If set to ``no`` "
"only administrators may change the user's password - users may update their "
"own password if they're still logged in and they have the required :doc:"
"`permission </manage/roles/user-preferences-permissions>`."
msgstr ""

#: ../settings/security/base.rst:0
msgid "Figure showing activated \"Lost Password\" setting"
msgstr ""

#: ../settings/security/base.rst:49
msgid ""
"With third party authentications - but especially LDAP - you may want to "
"disable this function. Zammad **will not** change third party login "
"passwords and instead set or change the local password!"
msgstr ""

#: ../settings/security/base.rst:56
msgid "Password Login"
msgstr ""

#: ../settings/security/base.rst:60
msgid ""
"Activates the username & password login by default and if no third-party "
"login is activated. Disabling password login on the Zammad login page only "
"takes effect if you enable any :doc:`third-party`."
msgstr ""

#: ../settings/security/base.rst:64
msgid "See :doc:`third-party` for supported third-party logins."
msgstr ""

#: ../settings/security/base.rst:0
msgid "Figure showing de-activated \"Password Login\" setting"
msgstr ""

#: ../settings/security/base.rst:77
msgid ""
"To help administrators to overcome \"login issues\", Zammad automatically "
"offers a password request for administrator users. This allows you to adjust "
"Third-Party applications even if the login does no longer work!"
msgstr ""

#: ../settings/security/base.rst:84
msgid "Session Timeout"
msgstr ""

#: ../settings/security/base.rst:86
msgid ""
"All settings below by default are set to ``4 weeks``. Session Timeout "
"defines the life time of a users session. As soon as it's reached, Zammad "
"will automatically log off the session in question."
msgstr ""

#: ../settings/security/base.rst:91
msgid ""
"Zammad takes the highest value set assigned for the user based on the "
"permissions."
msgstr ""

#: ../settings/security/base.rst:94
msgid "``admin``"
msgstr ""

#: ../settings/security/base.rst:96
msgid "``ticket.customer``"
msgstr ""

#: ../settings/security/base.rst:97
msgid "``default`` (fallback if user doesn't have above permissions set)"
msgstr ""

#: ../settings/security/base.rst:99
msgid ""
"All settings act independently from each other allowing you to disable the "
"timeouts for e.g. admins, but not agents."
msgstr ""

#: ../settings/security/base.rst:115
#: ../system/integrations/checkmk/api-reference.rst:13
msgid "Example"
msgstr ""

#: ../settings/security/base.rst:107
msgid "Let's suppose you configured the following session timeouts"
msgstr ""

#: ../settings/security/base.rst:104
msgid "default: 3 weeks"
msgstr ""

#: ../settings/security/base.rst:105
msgid "admin: 2 weeks"
msgstr ""

#: ../settings/security/base.rst:106
msgid "ticket.agent: 4 weeks"
msgstr ""

#: ../settings/security/base.rst:107
msgid "ticket.customer: 1 week"
msgstr ""

#: ../settings/security/base.rst:115
msgid "This results in the following situations"
msgstr ""

#: ../settings/security/base.rst:110
msgid "a user with ``admin`` permission will have a timeout of 2 weeks"
msgstr ""

#: ../settings/security/base.rst:111
msgid ""
"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout "
"of 2 weeks"
msgstr ""

#: ../settings/security/base.rst:113
msgid ""
"a user with ``ticket.customer`` permission will have a timeout of 1 week"
msgstr ""

#: ../settings/security/base.rst:115
msgid ""
"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` "
"permissions will have a timeout of 3 weeks"
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 "
"might be addressed in the future by `#1169 <https://github.com/zammad/zammad/"
"issues/1169>`_."
msgstr ""

#: ../settings/security/password.rst:14
msgid "**Exception for admins**"
msgstr ""

#: ../settings/security/password.rst:16
msgid ""
"Please note that below password policies *do not* affect administrators "
"setting passwords on user accounts. While this seems strange and not safe we "
"believe that an administrator knowing an user's password is insecure as well."
msgstr ""

#: ../settings/security/password.rst:21
msgid "The suggested workflow is either:"
msgstr ""

#: ../settings/security/password.rst:23
msgid ""
"to use third party logins to not require local passwords at all **- or -**"
msgstr ""

#: ../settings/security/password.rst:25
msgid "to require your *user to reset the password* upon first login."
msgstr ""

#: ../settings/security/password.rst:27
msgid ""
"This way administrators are not required to set a user's password at all!"
msgstr ""

#: ../settings/security/password.rst:31
msgid "Maximum Failed Logins"
msgstr ""

#: ../settings/security/password.rst:33
msgid ""
"You can choose a value between ``4`` and ``20``. This defines how often a "
"login to a user account may fail until Zammad will lock it. Your users can "
"always use the \"forgot password\" function to change their password and "
"unlock their account."
msgstr ""

#: ../settings/security/password.rst:38
msgid "The default value is ``10``."
msgstr ""

#: ../settings/security/password.rst:42
msgid "Beside changing the user's password, you can also unlock accounts via"
msgstr ""

#: ../settings/security/password.rst:44
msgid ":ref:`user management list <locked-user-accounts>`"
msgstr ""

#: ../settings/security/password.rst:45
msgid ":docs:`console </admin/console/working-on-users.html>`"
msgstr ""

#: ../settings/security/password.rst:46
msgid ":docs:`API </api/user.html>`"
msgstr ""

#: ../settings/security/password.rst:50
msgid "Failed logins via LDAP no longer lock accounts."
msgstr ""

#: ../settings/security/password.rst:53
msgid "2 Lower Case And 2 Upper Case Characters"
msgstr ""

#: ../settings/security/password.rst:55
msgid ""
"You can add complexity to passwords by enforcing at least 2 upper and lower "
"case characters."
msgstr ""

#: ../settings/security/password.rst:58 ../settings/security/password.rst:83
msgid "The default value is ``no``."
msgstr ""

#: ../settings/security/password.rst:62
msgid "Minimum Length"
msgstr ""

#: ../settings/security/password.rst:64
msgid ""
"This defines the minimum password length required for users to provide (from "
"``4`` to ``20``)."
msgstr ""

#: ../settings/security/password.rst:67
msgid "The default value is ``6``."
msgstr ""

#: ../settings/security/password.rst:71
msgid "Digit Required"
msgstr ""

#: ../settings/security/password.rst:73
msgid "This enforces your users to use at least one digit within the password."
msgstr ""

#: ../settings/security/password.rst:75
msgid "The default value is ``yes``."
msgstr ""

#: ../settings/security/password.rst:78
msgid "Special Character Required"
msgstr ""

#: ../settings/security/password.rst:80
msgid ""
"This setting allows you to improve your password quality even more by "
"enforcing the password to contain at least one special character."
msgstr ""

#: ../settings/security/ssl-certificates.rst:2
msgid "SSL Certificates"
msgstr ""

#: ../settings/security/ssl-certificates.rst:7
msgid ""
"Zammad offers the possibility to upload custom certificates and custom "
"Certificate Authority (CA) certificates. This can be useful if you want to "
"connect Zammad the secure way to other systems which are using custom "
"certificates."
msgstr ""

#: ../settings/security/ssl-certificates.rst:12
msgid ""
"An example usecase might be: You have an internal LDAP server that is not "
"accessible from the internet, and you want a SSL-encrypted connection, using "
"a custom certificate."
msgstr ""

#: ../settings/security/ssl-certificates.rst:19
msgid ""
"You should have an existing custom certificate file and/or a custom CA "
"certificate file, which you want to add to Zammad. As filetype ``.crt`` is "
"supported and the certificate format has to be PEM (Base64 ASCII)."
msgstr ""

#: ../settings/security/ssl-certificates.rst:25
msgid ""
"When you import a custom CA certificate, all certificates generated with "
"this are trusted. This can be useful if you have more than one system/"
"certificate you want to connect to and the certificates are issued from the "
"same custom CA."
msgstr ""

#: ../settings/security/ssl-certificates.rst:31
msgid "Add a Certificate"
msgstr ""

#: ../settings/security/ssl-certificates.rst:33
msgid ""
"To add a custom certificate or a custom CA certificate, head over to the "
"Admin panel > Settings > Security > SSL Certificates. Here you can find a "
"\"Add SSL Certificate\" button. In the dialog you can either select a "
"certificate file or paste the content of the certificate:"
msgstr ""

#: ../settings/security/ssl-certificates.rst:None
msgid "Screenshot showing certificate adding dialog"
msgstr ""

#: ../settings/security/ssl-certificates.rst:43
msgid ""
"After selecting a file or pasting the content of the certificate, click on "
"the \"Add\" button to finally upload it to Zammad. Then, the certificates "
"are immediately effective, no restart or similar required."
msgstr ""

#: ../settings/security/ssl-certificates.rst:49
msgid ""
"Please note that only single certificate files are supported. That means if "
"you want to import a certificate / CA certificate, it must contain **only "
"one** certificate."
msgstr ""

#: ../settings/security/ssl-certificates.rst:54
msgid "Certificate Overview"
msgstr ""

#: ../settings/security/ssl-certificates.rst:56
msgid ""
"After you added a certificate, you can see a table with information for each "
"added certificate:"
msgstr ""

#: ../settings/security/ssl-certificates.rst:None
msgid "Screenshot showing table of added certificates"
msgstr ""

#: ../settings/security/ssl-certificates.rst:64
msgid ""
"Here you can download the certificate or delete it, if you don't need it "
"anymore."
msgstr ""

#: ../settings/security/ssl-certificates.rst:68
msgid "Deleting Certificates"
msgstr ""

#: ../settings/security/ssl-certificates.rst:70
msgid ""
"If you want to delete a specific certificate, you can do it by clicking on "
"the menu in the actions column and selecting delete:"
msgstr ""

#: ../settings/security/ssl-certificates.rst:None
msgid "Screenshot showing certificate deletion button"
msgstr ""

#: ../settings/security/ssl-certificates.rst:79
msgid "Downloading Certificates"
msgstr ""

#: ../settings/security/ssl-certificates.rst:81
msgid ""
"If you want to download your certificates, you can do this as well via "
"corresponding action buttons."
msgstr ""

#: ../settings/security/ssl-certificates.rst:None
msgid "Screenshot showing certificate download button"
msgstr ""

#: ../settings/security/third-party.rst:13
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:10
msgid ""
"You can deactivate logging in via :ref:`security_password_login` if any of "
"the mentioned authentication providers are enabled in your instance."
msgstr ""

#: ../settings/security/third-party.rst:28
msgid ""
"We're currently missing documentation for the following login providers:"
msgstr ""

#: ../settings/security/third-party.rst:30
msgid "LinkedIn"
msgstr ""

#: ../settings/security/third-party.rst:31
msgid "Weibo"
msgstr ""

#: ../settings/security/third-party.rst:36
msgid "Automatic Account Link on Initial Logon"
msgstr ""

#: ../settings/security/third-party.rst:38
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:43
msgid ""
"This means that the user has to manually link authentication providers to "
"their accounts (for more about this :user-docs:`consult the user "
"documentation </extras/profile-and-settings.html>`)."
msgstr ""

#: ../settings/security/third-party.rst:47
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:51
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:61
msgid "Automatic Account Linking Notification"
msgstr ""

#: ../settings/security/third-party.rst:65
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:69
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:72
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:86
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:90
msgid "This means it only affects:"
msgstr ""

#: ../settings/security/third-party.rst:92
msgid "manual account linking within the third-party page of the users profile"
msgstr ""

#: ../settings/security/third-party.rst:93
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.rst:101
msgid "No User Creation on Logon"
msgstr ""

#: ../settings/security/third-party.rst:103
msgid ""
"By default, Zammad will create a new user account if the user logs in via a "
"third-party application and the account doesn't exist yet."
msgstr ""

#: ../settings/security/third-party.rst:106
msgid ""
"If you want to prevent Zammad from creating new accounts on logon, you can "
"disable this feature by setting ``No user creation on logon`` to ``yes``."
msgstr ""

#: ../settings/security/third-party.rst:None
msgid "Screenshot showing the \"no user creation on logon\" 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: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:46
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:42
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-fqdn/auth/gitlab/callback\" where "
"zammad-fqdn 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 "Just select *read_user* under scopes as in the screenshot and save it."
msgstr ""

#: ../settings/security/third-party/gitlab.rst:21
msgid "Configure Zammad as Gitlab App"
msgstr ""

#: ../settings/security/third-party/gitlab.rst:23
msgid ""
"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH "
"Applications Dashboard and your Gitlab-URL in the \"SITE\" field."
msgstr ""

#: ../settings/security/third-party/gitlab.rst:None
msgid "Gitlab config in Zammad admin interface"
msgstr ""

#: ../settings/security/third-party/gitlab.rst:30
msgid ""
"After you configured the Gitlab credentials and activated the login method, "
"you should see a new icon on the login page."
msgstr ""

#: ../settings/security/third-party/gitlab.rst:None
msgid "Gitlab logo on login page"
msgstr ""

#: ../settings/security/third-party/gitlab.rst:36
msgid ""
"If you click on the icon you will be redirected to Gitlab and see something "
"similar to this:"
msgstr ""

#: ../settings/security/third-party/gitlab.rst:None
msgid "Gitlab oauth page"
msgstr ""

#: ../settings/security/third-party/google.rst:2
msgid "Google"
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 saving the consent screen information, you can go to "
"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials."
msgstr ""

#: ../settings/security/third-party/google.rst:28
msgid ""
"Fill in the necessary information as follows and replace ``zammad_host`` "
"with your FQDN:"
msgstr ""

#: ../settings/security/third-party/google.rst:31
msgid "**Application 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:10
msgid ""
"This documentation part does not cover our :doc:`📧 Microsoft 365 email "
"channel </channels/microsoft365/index>`."
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:30
#: ../settings/security/third-party/microsoft.rst:53
msgid "Supported account types:"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:22
msgid ""
"Please note that Zammad only supports these account types (App dependent):"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:24
msgid ""
"Accounts in this organizational directory only (Default Directory only - "
"Single tenant)"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:26
msgid ""
"Accounts in any organizational directory (Any Azure AD directory - "
"Multitenant)"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:28
msgid ""
"Accounts in any organizational directory (Any Azure AD directory - "
"Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:35
msgid "Avatars of signing in users:"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:33
msgid ""
"Zammad currently ignores user avatars. If the user is registered with e.g. "
"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:"
"`Zammad Image Service </settings/system/index>` for more."
msgstr ""

#: ../settings/security/third-party/microsoft.rst:38
msgid "Step 1 - Register a Microsoft App for Zammad"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:40
msgid ""
"Login to the `Microsoft Azure Portal <https://portal.azure.com/>`_ 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:46
msgid "Name:"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:45
msgid ""
"Any meaningful name fitting, this name will be displayed to users trying to "
"authenticate with this app."
msgstr ""

#: ../settings/security/third-party/microsoft.rst:49
msgid "Choose one of the above mentioned account types (see Limitations)."
msgstr ""

#: ../settings/security/third-party/microsoft.rst:51
msgid ""
"The correct account type depends on your use case. If you want to use the "
"authentication internal only, choose the first option. If you're unsure, use "
"the \"Help me choose...\" link."
msgstr ""

#: ../settings/security/third-party/microsoft.rst:58
msgid "Redirect URI (optional):"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:56
msgid ""
"Select web and provide your callback URL. The callback URL looks like this: "
"``https://zammad.domain.tld/auth/microsoft_office365/callback``"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:None
msgid "Screencast showing how to register a Microsoft app"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:71
msgid "Within  **API permissions** add the following permissions:"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:66
msgid "OpenId permissions"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:69
msgid "``User.Read``"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:71
msgid "Contacts"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:71
msgid "``Contacts.Read``"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:73
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:80
msgid ""
"Within **Certificates & secrets** create a new client secret. Note down the "
"returned secret **value** for later. **Do not** use the secret ID!"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:None
msgid "Screencast showing how to create a new app secret"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:88
msgid ""
"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:98
msgid "Step 2 - Add App Credentials to Zammad"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:100
msgid ""
"Navigate to Security > Third-party Applications (Tab) within Zammad's admin "
"settings. Scroll down to the section *Authentication via Microsoft* and fill "
"in the required information."
msgstr ""

#: ../settings/security/third-party/microsoft.rst:105
msgid "App ID:"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:105
msgid "This is your *Application (client) ID*."
msgstr ""

#: ../settings/security/third-party/microsoft.rst:108
msgid "App secret:"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:108
msgid "This is your *client secret* (value)."
msgstr ""

#: ../settings/security/third-party/microsoft.rst:113
msgid "App Tenant ID:"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:111
msgid ""
"**optional** only required for apps that use account type *Accounts in this "
"organizational directory only (Default Directory only - Single tenant).*"
msgstr ""

#: ../settings/security/third-party/microsoft.rst:115
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/openid-connect.rst:2
msgid "OpenID Connect"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:4
msgid ""
"OpenID is an easy and safe way for people to reuse an existing account and "
"user profile from an OpenID provider. Connect your OpenID provider (OP) as a "
"single sign-on (SSO) method."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:8
msgid ""
"The relying party (RP) is Zammad and the OpenID provider is a software "
"service that you either host or subscribe to (e.g. `Keycloak <https://www."
"keycloak.org/>`_)."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:13
msgid ""
"This guide assumes you are already using OpenID Connect within your "
"organization (i.e. that your OP is fully set up)."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:15
msgid ""
"The current implementation of OpenID Connect in Zammad requires OpenID "
"Connect Discovery to simplify the configuration."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:17
msgid ""
"The connection between Zammad and your OP has to be secure. Both systems "
"must be reachable via HTTPS. Self-signed certificates are not supported."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:20
msgid "Our instructions are based on connecting Zammad with Keycloak."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:21
msgid "PKCE is currently only supporting SHA256 as code challenge method."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:24
msgid "Step 1: Configure Your OP"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:27
msgid "Add a new Client"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:29
msgid "Create a new client in your OP with the following settings:"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:33
msgid "General settings"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:32
msgid "Client type: OpenID Connect"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:33
msgid "Client ID: ``zammad`` (or any other name you prefer)"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:37
msgid "Capability config"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:36
msgid "Client authentication: Off"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:37
msgid "Authentication flow: Standard flow"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:42
msgid "Login settings"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:40
msgid ""
"Valid redirect URIs: ``https://your.zammad.domain/auth/openid_connect/"
"callback``"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:41
msgid "Valid post logout redirect URIs: ``https://your.zammad.domain/*``"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:42
msgid "Web origins: ``+``"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:44
msgid ""
"In the **Logout settings** for the newly created client, set the "
"**Backchannel logout URL** to ``https://your.zammad.domain/auth/"
"openid_connect/backchannel_logout`` and switch on **Backchannel logout "
"session required**."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:49
msgid ""
"If you would like to use `PKCE <https://oauth.net/2/pkce/>`_, you need to "
"switch to the **Advanced** tab and select **S256** in **Advanced settings** "
"as the code challenge method for PKCE."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:54
msgid "Step 2: Configure Zammad"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:56
msgid ""
"Enable OpenID Connect and enter your OP's details in the Admin Panel under "
"**Settings > Security > Third Party Applications > Authentication via OpenID "
"Connect**:"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:None
msgid "Example configuration of OpenID Connect"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:69
#: ../settings/security/third-party/saml.rst:102
msgid "Display name"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:66
msgid ""
"Allows you to define a custom button name for OpenID Connect. This helps "
"your users to understand better what the button on the login page does."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:69
msgid "Defaults to ``OpenID Connect``."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:72
msgid "Identifier"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:72
msgid "The client ID you defined in your OP."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:75
msgid "Issuer"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:75
msgid "The issuer URL of your OP. Used for discovery."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:79
msgid "UID field"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:78
msgid ""
"Here you can define an attribute that uniquely identifies the user. If "
"unset, ``sub`` is used."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:83
msgid "Scopes"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:82
msgid ""
"The scopes that Zammad should request from the OP. Defaults to ``openid``, "
"``email`` and ``profile``."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:86
msgid "PKCE"
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:86
msgid "Currently only SHA256 as code challenge method is supported."
msgstr ""

#: ../settings/security/third-party/openid-connect.rst:88
msgid ""
"See :ref:`automatic account linking <automatic-account-linking>` for details "
"on how to link existing Zammad accounts to OP accounts."
msgstr ""

#: ../settings/security/third-party/saml.rst:2
msgid "SAML"
msgstr ""

#: ../settings/security/third-party/saml.rst:7
msgid ""
"Connect your SAML (Security Assertion Markup Language) identity provider as "
"a single sign-on (SSO) method. 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 <https://www."
"keycloak.org/>`_, `Redhat SSO Server <https://access.redhat.com/products/red-"
"hat-single-sign-on>`_, `ADFS <https://docs.microsoft.com/en-us/windows-"
"server/identity/active-directory-federation-services>`_, or `Okta <https://"
"www.okta.com/>`_)."
msgstr ""

#: ../settings/security/third-party/saml.rst:19
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:23
msgid "Basic Configuration"
msgstr ""

#: ../settings/security/third-party/saml.rst:25
msgid ""
"This section describes the setup of an IdP in a general way. See :ref:`saml-"
"guides` for setup guides for Keycloak and Microsoft SAML."
msgstr ""

#: ../settings/security/third-party/saml.rst:29
msgid "Configure Your IdP"
msgstr ""

#: ../settings/security/third-party/saml.rst:32
msgid "Add Zammad as a Client/App"
msgstr ""

#: ../settings/security/third-party/saml.rst:34
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:37
msgid ""
"If your IdP doesn't support XML import, you will have to configure Zammad as "
"a new client/app manually using the above XML metadata file for reference."
msgstr ""

#: ../settings/security/third-party/saml.rst:40
msgid "For instance, when you see this tag:"
msgstr ""

#: ../settings/security/third-party/saml.rst:46
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:51
msgid "Set Up User Attribute Mapping"
msgstr ""

#: ../settings/security/third-party/saml.rst:53
msgid ""
"Zammad requests the following user attributes (or “properties”) from the IdP:"
msgstr ""

#: ../settings/security/third-party/saml.rst:55
msgid "Email address (``email``)"
msgstr ""

#: ../settings/security/third-party/saml.rst:56
msgid "Full name (``name``)"
msgstr ""

#: ../settings/security/third-party/saml.rst:57
msgid "Given name (``first_name``)"
msgstr ""

#: ../settings/security/third-party/saml.rst:58
msgid "Family name (``last_name``)"
msgstr ""

#: ../settings/security/third-party/saml.rst:60
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:68
msgid "Configuration Guides"
msgstr ""

#: ../settings/security/third-party/saml.rst:70
msgid "You can find specific configuration guides for:"
msgstr ""

#: ../settings/security/third-party/saml.rst:72
msgid ":doc:`Keycloak <./saml/saml-keycloak>`"
msgstr ""

#: ../settings/security/third-party/saml.rst:73
msgid ":doc:`Microsoft SAML <./saml/saml-microsoft>`"
msgstr ""

#: ../settings/security/third-party/saml.rst:75
msgid ""
"If your are using another IdP, adapt it to your needs. For a description of "
"the fields in Zammad, read on below."
msgstr ""

#: ../settings/security/third-party/saml.rst:88
msgid "General Zammad Configuration"
msgstr ""

#: ../settings/security/third-party/saml.rst:90
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 part 1"
msgstr ""

#: ../settings/security/third-party/saml.rst:99
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:102
msgid "Defaults to ``SAML``."
msgstr ""

#: ../settings/security/third-party/saml.rst:106
msgid "IDP SSO target URL"
msgstr ""

#: ../settings/security/third-party/saml.rst:105
msgid ""
"This is the target URL Zammad shall redirect to when the user presses the "
"SAML button."
msgstr ""

#: ../settings/security/third-party/saml.rst:110
msgid "IDP single logout target URL"
msgstr ""

#: ../settings/security/third-party/saml.rst:109
msgid ""
"This is the URL to which the single logout request and response should be "
"sent."
msgstr ""

#: ../settings/security/third-party/saml.rst:114
msgid "IDP certificate"
msgstr ""

#: ../settings/security/third-party/saml.rst:113
msgid ""
"The public certificate of your IDP for Zammad to verify during the callback "
"phase."
msgstr ""

#: ../settings/security/third-party/saml.rst:128
msgid "IDP certificate fingerprint"
msgstr ""

#: ../settings/security/third-party/saml.rst:117
msgid ""
"The fingerprint of your IDPs public certificate to verify during callback "
"phase."
msgstr ""

#: ../settings/security/third-party/saml.rst:120
msgid "🔏 **For the IdP certificate / certificate fingerprint:**"
msgstr ""

#: ../settings/security/third-party/saml.rst:122
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 <https://www.schneier.com/blog/archives/2005/02/"
"sha1_broken.html>`_.)"
msgstr ""

#: ../settings/security/third-party/saml.rst:127
msgid ""
"**Keycloak users:** Find your certificate in the Keycloak admin panel under "
"**Realm Settings > Keys > Algorithm: RS256 > Certificate**."
msgstr ""

#: ../settings/security/third-party/saml.rst:134
msgid "Name identifier format"
msgstr ""

#: ../settings/security/third-party/saml.rst:131
msgid ""
"This is the unique identifiers field type. Usually it should be ``urn:oasis:"
"names:tc:SAML:1.1:nameid-format:emailAddress``."
msgstr ""

#: ../settings/security/third-party/saml.rst:134
msgid "Zammad **expects an email address as unique identifier**!"
msgstr ""

#: ../settings/security/third-party/saml.rst:138
msgid "UID attribute name"
msgstr ""

#: ../settings/security/third-party/saml.rst:137
msgid ""
"Here you can define an attribute that uniquely identifies the user. If "
"unset, the name identifier returned by the IDP is used."
msgstr ""

#: ../settings/security/third-party/saml.rst:None
msgid "Example configuration of SAML part 2"
msgstr ""

#: ../settings/security/third-party/saml.rst:146
msgid ""
"Decide if the certificate for the connection to the IdP service has to be "
"verified or not (default: ``yes``)."
msgstr ""

#: ../settings/security/third-party/saml.rst:152
msgid "Signing & Encrypting"
msgstr ""

#: ../settings/security/third-party/saml.rst:152
msgid ""
"Define if you want to sign, encrypt, do both or nothing for the requests."
msgstr ""

#: ../settings/security/third-party/saml.rst:162
msgid "Certificate (PEM)"
msgstr ""

#: ../settings/security/third-party/saml.rst:155
msgid ""
"Paste the public certificate of your Zammad SAML client, if you want to "
"encrypt the requests."
msgstr ""

#: ../settings/security/third-party/saml.rst:158
msgid "Make sure the certificate is:"
msgstr ""

#: ../settings/security/third-party/saml.rst:160
msgid "already valid and not yet expired"
msgstr ""

#: ../settings/security/third-party/saml.rst:161
msgid "no CA certificate"
msgstr ""

#: ../settings/security/third-party/saml.rst:162
msgid "valid for signing and encrypting"
msgstr ""

#: ../settings/security/third-party/saml.rst:168
msgid "Private key (PEM)"
msgstr ""

#: ../settings/security/third-party/saml.rst:165
msgid ""
"Paste the private key of your Zammad SAML client here, if you want to sign "
"the requests."
msgstr ""

#: ../settings/security/third-party/saml.rst:168
msgid "Make sure the key is an RSA key with a length of at least 2048 bits."
msgstr ""

#: ../settings/security/third-party/saml.rst:171
msgid "Private key secret"
msgstr ""

#: ../settings/security/third-party/saml.rst:171
msgid "If your private key is secured with a secret, you can provide it here."
msgstr ""

#: ../settings/security/third-party/saml.rst:175
msgid "Your callback URL"
msgstr ""

#: ../settings/security/third-party/saml.rst:174
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:177
msgid ""
"After saving your input by clicking on the \"Submit\" button, Zammad "
"verifies the provided keys/certificates (e.g. if they are valid for signing/"
"encrypting and if they aren't expired)."
msgstr ""

#: ../settings/security/third-party/saml.rst:182
msgid ""
"See :ref:`automatic account linking <automatic-account-linking>` for details "
"on how to link existing Zammad accounts to IdP accounts."
msgstr ""

#: ../settings/security/third-party/saml.rst:188
msgid "Automatic account linking doesn't work"
msgstr ""

#: ../settings/security/third-party/saml.rst:189
msgid ""
"Have you double-checked your IdP's user attribute mapping configuration?"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:2
msgid "SAML with Keycloak"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:5
msgid "Step 1: Keycloak Configuration"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:7
msgid ""
"**To add Zammad as a client,** save the XML configuration to disk (``https://"
"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > "
"Import client** in the Keycloak admin panel."
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:13
msgid ""
"To help Zammad **match its own user accounts to Keycloak users**, create a "
"user attribute (or “property”) mapper. In **Clients list**, click on your "
"newly created Client ID, choose the tab **Client scopes** and click on the "
"link which refers to your Zammad instance. Choose **Add mapper > By "
"configuration > User Property** and create a mapper with the following "
"entries:"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:22
msgid "**Name**"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:24
msgid "**Mapper Type**"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:25
msgid "``User Property``"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:26
msgid "**Property**"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:27
msgid "``emailAddress``"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:28
msgid "**SAML Attribute Name**"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:30
msgid "**SAML Attribute NameFormat**"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:31
msgid "``basic``"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:33
msgid ""
"In the example above, we're telling Zammad that whenever it receives a SAML "
"login request, it should take the ``email`` property from Keycloak, look for "
"a Zammad user with the same ``email`` attribute, and create a new session "
"for that user."
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:39
msgid ""
"If your Keycloak users' email addresses are stored on another property (*e."
"g.,* ``username``), adjust accordingly."
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:42
msgid ""
"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/"
"saml/metadata``) in the field **Master SAML Processing URL**."
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:46
msgid "You also need to enable **Sign assertions**."
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:49
msgid "2. Configure Zammad"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:51
#: ../settings/security/third-party/saml/saml-microsoft.rst:53
msgid "Log in to Zammad as an administrator"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:52
#: ../settings/security/third-party/saml/saml-microsoft.rst:54
msgid ""
"In the admin panel go to \"Settings\" > \"Security\" > \"Third-party "
"Applications\" > \"Authentication via SAML\""
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:54
#: ../settings/security/third-party/saml/saml-microsoft.rst:56
msgid "Provide the following information:"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:56
msgid ""
"SAML IdP Login URL: ``https://your.domain/realms/your-realm/protocol/saml``"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:57
msgid ""
"SAML IdP Logout URL: ``https://your.domain/realms/your-realm/protocol/saml``"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:59
#: ../settings/security/third-party/saml/saml-microsoft.rst:61
msgid ""
"Name Identifier Format: ``urn:oasis:names:tc:SAML:1.1:nameid-format:"
"emailAddress``"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:60
#: ../settings/security/third-party/saml/saml-microsoft.rst:62
msgid ""
"SAML IdP Certificate: Upload the previously downloaded Base64 certificate."
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:61
#: ../settings/security/third-party/saml/saml-microsoft.rst:63
msgid "Save the settings"
msgstr ""

#: ../settings/security/third-party/saml/saml-keycloak.rst:64
#: ../settings/security/third-party/saml/saml-microsoft.rst:72
msgid ""
"Read on at :ref:`saml-zammad` for a description of the specific fields in "
"Zammad."
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:2
msgid "SAML with Microsoft 365"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:5
msgid "1. Register Zammad as an Application in Microsoft Entra ID"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:7
msgid "Log in to the Microsoft Entra admin center with administrative rights"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:8
msgid ""
"Navigate to \"Identity\" > \"Applications\" > \"Enterprise Applications\""
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:9
msgid "Click \"New Application\" and select \"Create your own application\""
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:10
msgid "Enter a name for the application, e.g. \"Zammad SAML Integration\""
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:11
msgid ""
"Choose \"Integrate any other application you don't find in the gallery\", "
"then click \"Create\""
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:15
msgid "2. Configure SAML-based Single Sign-On (SSO)"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:17
msgid "After the application is created, go to its overview page"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:18
msgid "Select \"Single sign-on\" from the left-hand menu"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:19
msgid "Choose \"SAML\" as the sign-on method"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:20
msgid "In the \"Basic SAML Configuration\" section, click \"Edit\":"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:22
msgid ""
"Identifier (Entity ID): Use Zammad's Entity ID, which can be found at "
"``https://your.zammad.domain/auth/saml/metadata``"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:24
msgid ""
"Reply URL (Assertion Consumer Service URL): Set it to ``https://your.zammad."
"domain/auth/saml/callback``"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:27
msgid "Save the configuration"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:30
msgid "3. Configure User Attributes and Claims Mapping"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:32
msgid ""
"In the \"Attributes & Claims\" section, click \"Edit\". By default, some "
"claims like User Principal Name, Email Address, First Name, and Last Name "
"are already configured."
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:None
msgid ""
"Screenshots showing \"Attribute & Claims\" configuration in Entra admin "
"center"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:41
msgid "4. Download the SAML Certificate"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:43
msgid ""
"In the \"SAML Signing Certificate\" section, download the \"Certificate "
"(Base64)\":"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:None
msgid "Screenshot showing the highlighted certificate export already"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:51
msgid "5. Configure Zammad"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:58
msgid ""
"IDP SSO target URL: The Login URL from the Microsoft Entra Admin Center."
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:59
msgid ""
"IDP single logout target URL: The Logout URL from the Microsoft Entra Admin "
"Center."
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:66
msgid "6. Assign Users"
msgstr ""

#: ../settings/security/third-party/saml/saml-microsoft.rst:68
msgid ""
"In Microsoft Entra ID, assign the relevant users to the Zammad application "
"to grant them access."
msgstr ""

#: ../settings/security/third-party/twitter.rst:4
msgid ""
"It is possible to create a quick login for your helpdesk via Twitter. To do "
"so, you need to follow these steps:"
msgstr ""

#: ../settings/security/third-party/twitter.rst:8
msgid "Register Twitter App"
msgstr ""

#: ../settings/security/third-party/twitter.rst:10
msgid "Go to https://dev.twitter.com/apps and login with your account."
msgstr ""

#: ../settings/security/third-party/twitter.rst:15
msgid "Click on \"Create App\""
msgstr ""

#: ../settings/security/third-party/twitter.rst:None
msgid "new app page"
msgstr ""

#: ../settings/security/third-party/twitter.rst:20
msgid ""
"Enter app settings. As \"Callback URL\" you need to enter ``https://"
"zammad_host/api/v1/external_credentials/twitter/callback``. You need to "
"replace ``zammad_host`` with the domain of your Zammad system."
msgstr ""

#: ../settings/security/third-party/twitter.rst:24
msgid ""
"After the app has been created, update the application icon and organization "
"attributes."
msgstr ""

#: ../settings/security/third-party/twitter.rst:None
msgid "set permissions to receive and send direct messages"
msgstr ""

#: ../settings/security/third-party/twitter.rst:30
msgid ""
"Next we need to set ``read, write and access direct messages`` permissions "
"for the app."
msgstr ""

#: ../settings/security/third-party/twitter.rst:None
msgid "click on Keys & Access Token, note them"
msgstr ""

#: ../settings/security/third-party/twitter.rst:36
msgid ""
"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and "
"\"Consumer Secret\"."
msgstr ""

#: ../settings/security/third-party/twitter.rst:40
msgid "Configure Zammad as Twitter App"
msgstr ""

#: ../settings/security/third-party/twitter.rst:42
msgid ""
"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" "
"Section."
msgstr ""

#: ../settings/security/third-party/twitter.rst:None
msgid "Admin > Security > Third Party Applications"
msgstr ""

#: ../settings/security/third-party/twitter.rst:48
msgid ""
"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the "
"\"Submit\" button."
msgstr ""

#: ../settings/security/third-party/twitter.rst:51
msgid ""
"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login "
"via Zammad login page."
msgstr ""

#: ../settings/security/two-factor.rst:11
msgid "Two-factor Authentication Methods"
msgstr ""

#: ../settings/security/two-factor.rst:2
msgid "Two-Factor Authentication"
msgstr ""

#: ../settings/security/two-factor.rst:4
msgid ""
"Two-factor authentication (2FA) enhances the security of Zammad accounts by "
"adding an extra layer of verification beyond a password. It requires users "
"to provide two different types of authentication factors, typically "
"something they know (like a password) and something they possess (like a "
"mobile device or a security token), to ensure that only authorized "
"individuals can access the account."
msgstr ""

#: ../settings/security/two-factor.rst:19
msgid "Enable Recovery Codes"
msgstr ""

#: ../settings/security/two-factor.rst:21
msgid ""
"Recovery codes are one-time use security codes that can be used by the user "
"if they lose access to their other two-factor authentication methods. They "
"cannot be used on their own, they can only be activated if at least one two-"
"factor authentication method is enabled."
msgstr ""

#: ../settings/security/two-factor.rst:None
msgid "Enable Recovery Codes Setting"
msgstr ""

#: ../settings/security/two-factor.rst:30
msgid ""
"Recovery codes can only be used as a backup method. If enabled, they will be "
"automatically generated for the user once they set up their initial two-"
"factor authentication method."
msgstr ""

#: ../settings/security/two-factor.rst:34
msgid ""
"The user will be asked to print out or save the generated recovery codes in "
"a safe place. Once used, a recovery code cannot be reused."
msgstr ""

#: ../settings/security/two-factor.rst:37
msgid ""
"Users will also have an option to regenerate their recovery codes at any "
"time, which invalidates already existing recovery codes and provides them "
"with a list of fresh codes."
msgstr ""

#: ../settings/security/two-factor.rst:41
msgid ""
"After you enable this setting, when the user completes a setup of their "
"initial two-factor authentication method, they will be presented with a list "
"of recovery codes and instructed to save them for later use."
msgstr ""

#: ../settings/security/two-factor.rst:None
msgid "Recovery Codes Generation Modal Dialog"
msgstr ""

#: ../settings/security/two-factor.rst:50
msgid "Enforce the Set Up of the Two-Factor Authentication"
msgstr ""

#: ../settings/security/two-factor.rst:52
msgid ""
"In case you wish to require your users to set up at least one two-factor "
"authentication method for their account, you can do this by selecting "
"specific user roles the requirement applies to in **Enforced for user "
"roles** setting. Of course you must have at least one two-factor "
"authentication method enabled for this setting to take effect."
msgstr ""

#: ../settings/security/two-factor.rst:None
msgid "Enforced for User Roles Setting"
msgstr ""

#: ../settings/security/two-factor.rst:62
msgid ""
"After you change this setting, if the user has one of the selected roles on "
"their account, they will be forced to set up the two-factor authentication "
"upon next sign in or application reload."
msgstr ""

#: ../settings/security/two-factor.rst:66
msgid ""
"A modal dialog with instructions will be shown, and they will not be able to "
"do any work before they set up at least one two-factor method."
msgstr ""

#: ../settings/security/two-factor.rst:None
msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up"
msgstr ""

#: ../settings/security/two-factor.rst:74
msgid "Reset Two-Factor Authentication for a Specific User"
msgstr ""

#: ../settings/security/two-factor.rst:76
msgid ""
"In case an user isn't able to login anymore because of an inaccessible "
"second factor, you can reset the user's 2FA method."
msgstr ""

#: ../settings/security/two-factor.rst:79
msgid ""
"To do this, go to the user management and search for the relevant user. "
"After you found the account, click the button in the action column and "
"select \"Manage Two-Factor Authentication\":"
msgstr ""

#: ../settings/security/two-factor.rst:None
msgid "Context menu in action column in user management"
msgstr ""

#: ../settings/security/two-factor.rst:87
msgid ""
"After selecting this, you can see a dialog where you can either reset one "
"2FA method or reset all of the user's 2FA methods:"
msgstr ""

#: ../settings/security/two-factor.rst:None
msgid "Dialog for resetting user's 2FA method"
msgstr ""

#: ../settings/security/two-factor.rst:94
msgid ""
"Choose the fitting one, click on the corresponding \"Remove ...\" button and "
"confirm your action. The user now has to setup a new 2FA method, depending "
"on your 2FA configuration."
msgstr ""

#: ../settings/security/two-factor/authenticator-app.rst:2
msgid "Authenticator App"
msgstr ""

#: ../settings/security/two-factor/authenticator-app.rst:4
msgid ""
"The authenticator app method is a type of two-factor authentication that "
"uses a mobile application to generate one-time codes for account "
"verification. After setting up the authenticator app on their device, the "
"user links it to their Zammad account."
msgstr ""

#: ../settings/security/two-factor/authenticator-app.rst:12
msgid ""
"When logging in, the user is prompted to enter a time-sensitive code "
"generated by the app, in addition to their password. This code acts as the "
"second factor of authentication, providing an extra layer of security as it "
"changes periodically and is unique to the user's device."
msgstr ""

#: ../settings/security/two-factor/authenticator-app.rst:None
msgid "Security Code in Google Authenticator App"
msgstr ""

#: ../settings/security/two-factor/authenticator-app.rst:22
msgid ""
"The app generates codes based on a shared secret key stored securely on both "
"the user's device and the server, ensuring a synchronized and secure "
"authentication process. The method of generating the codes is sometimes also "
"called TOTP (time-based one-time password)."
msgstr ""

#: ../settings/security/two-factor/authenticator-app.rst:28
msgid "Enabling the Authenticator App Method"
msgstr ""

#: ../settings/security/two-factor/authenticator-app.rst:30
#: ../settings/security/two-factor/security-keys.rst:28
msgid "To enable the method, just toggle the switch on in the settings."
msgstr ""

#: ../settings/security/two-factor/authenticator-app.rst:None
msgid "Authenticator App Switch in Settings"
msgstr ""

#: ../settings/security/two-factor/authenticator-app.rst:36
msgid ""
"Now the users will be able to set up this two-factor authentication method "
"for their accounts via \"Avatar -> Profile -> Password & Authentication\". "
"Once they do, on next sign-in with password, they will be asked to provide "
"an additional security code generated by their mobile device."
msgstr ""

#: ../settings/security/two-factor/security-keys.rst:2
msgid "Security Keys"
msgstr ""

#: ../settings/security/two-factor/security-keys.rst:4
msgid ""
"The security keys method is a type of a two-factor authentication that uses "
"Web Authentication API in the browser for verifying user's identity. The "
"user can register multiple hardware or software security keys with their "
"Zammad account and then they can use it during the sign-in process."
msgstr ""

#: ../settings/security/two-factor/security-keys.rst:12
msgid ""
"When logging in, the user is prompted to provide the same security key they "
"registered with their account, in addition to their password. This key acts "
"as the second factor of authentication, providing an extra layer of security."
msgstr ""

#: ../settings/security/two-factor/security-keys.rst:None
msgid "Security Key dialog in Safari on macOS"
msgstr ""

#: ../settings/security/two-factor/security-keys.rst:21
msgid ""
"The type of the key can range from hardware USB sticks to passkeys stored in "
"a device of user's choice. Which type can be used depends on the browser "
"flavor and the platform of the user."
msgstr ""

#: ../settings/security/two-factor/security-keys.rst:26
msgid "Enabling the Security Keys Method"
msgstr ""

#: ../settings/security/two-factor/security-keys.rst:None
msgid "Security Keys Switch in Settings"
msgstr ""

#: ../settings/security/two-factor/security-keys.rst:34
msgid ""
"Now the users will be able to set up this two-factor authentication method "
"for their accounts via \"Avatar -> Profile -> Password & Authentication\". "
"Once they do, on next sign-in with password, they will be asked to provide "
"the same security key they registered during the setup."
msgstr ""

#: ../settings/system/system-selfhosted.include.rst:3
msgid ""
"Below settings are only available to self hosted users. In hosted "
"environments we're handling these settings for you to ensure service "
"stability."
msgstr ""

#: ../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:`/misc/variables` and notifications."
msgstr ""

#: ../settings/system/system-base.include.rst:1
msgid "It is automatically set by the *Getting Started wizard*."
msgstr ""

#: ../settings/system/system-base.include.rst:5
msgid "Changing this setting also changes callback URLs for your channels etc."
msgstr ""

#: ../settings/system/system-base.include.rst:6
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 :docs:`hidden settings </"
"admin/console/hidden-settings.html>` section."
msgstr ""

#: ../settings/system/network.rst:2
msgid "Network"
msgstr ""

#: ../settings/system/network.rst:8
msgid ""
"The proxy settings can only be saved after successfully testing the proxy "
"connection."
msgstr ""

#: ../settings/system/network.rst:15
msgid "Proxy Address."
msgstr ""

#: ../settings/system/network.rst:12
msgid ""
"Allows you to provide a proxy server if needed. This is relevant for network "
"communication by Zammad."
msgstr ""

#: ../settings/system/network.rst:15
msgid "It **does not** affect the update process or Elasticsearch."
msgstr ""

#: ../settings/system/network.rst:18
msgid "Username for proxy connection."
msgstr ""

#: ../settings/system/network.rst:18
msgid ""
"If your proxy server requires authentication, provide the username here."
msgstr ""

#: ../settings/system/network.rst:21
msgid "Password for proxy connection."
msgstr ""

#: ../settings/system/network.rst:21
msgid ""
"If your proxy server requires authentication, provide the password here."
msgstr ""

#: ../settings/system/network.rst:26
msgid "No proxy for the following hosts."
msgstr ""

#: ../settings/system/network.rst:24
msgid ""
"Exception list for hosts you can't or don't want to reach via proxy server."
msgstr ""

#: ../settings/system/network.rst:27
msgid "Default: ``localhost,127.0.0.0,::1``"
msgstr ""

#: ../settings/system/services.rst:2
msgid "Services"
msgstr ""

#: ../settings/system/services.rst:10
msgid "Image Service"
msgstr ""

#: ../settings/system/services.rst:5
msgid "Defines the backend for user and organization image lookups."
msgstr ""

#: ../settings/system/services.rst:7
msgid "Default: ``Zammad Image Service`` (active)"
msgstr ""

#: ../settings/system/services.rst:9
msgid ""
"Make sure your on premise installation has ``HTTPS`` access to ``images."
"zammad.com``."
msgstr ""

#: ../settings/system/services.rst:18
msgid "Geo Calendar Service"
msgstr ""

#: ../settings/system/services.rst:13
msgid ""
"Defines the backend for geo calendar lookups. Used for initial calendar "
"setup."
msgstr ""

#: ../settings/system/services.rst:16
msgid "Default: ``Zammad GeoCalendar Service`` (active)"
msgstr ""

#: ../settings/system/services.include.rst:2
msgid ""
"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad."
"com``."
msgstr ""

#: ../settings/system/services.rst:26
msgid "Geo IP Service"
msgstr ""

#: ../settings/system/services.rst:21
msgid ""
"Defines the backend for geo IP lookups. Shows also location of an IP address "
"if an IP address is shown."
msgstr ""

#: ../settings/system/services.rst:24
msgid "Default: ``Zammad GeoIP Service`` (active)"
msgstr ""

#: ../settings/system/services.rst:32
msgid "Geo Location Service"
msgstr ""

#: ../settings/system/services.rst:29
msgid ""
"Defines the backend for geo location lookups to store geo locations for "
"addresses."
msgstr ""

#: ../settings/system/services.rst:32
msgid ""
"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)"
msgstr ""

#: ../settings/system/services.rst:36
msgid ""
"You can find a detailed privacy information on what we store for how long on "
"our :docs:`Privacy Appendix </appendix/privacy.html>` inside of our System "
"Documentation."
msgstr ""

#: ../settings/system/storage.rst:2
msgid "Storage"
msgstr ""

#: ../settings/system/storage.rst:6
msgid ""
"Here you can define where Zammad stores attachments for tickets and the "
"knowledge base. By default, we're writing to the ``Database`` - you can "
"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this "
"case please have a look on the following instructions."
msgstr ""

#: ../settings/system/storage.rst:11
msgid ""
"If you have a busy Zammad instance, we strongly encourage you to use "
"filesystem storage instead of \"Database\". This will greatly improve system "
"performance (de-crease database load and size)."
msgstr ""

#: ../settings/system/storage.rst:19
msgid "Database"
msgstr ""

#: ../settings/system/storage.rst:17
msgid ""
"This is the default storage method. The attachments are stored directly in "
"the database. If your Zammad instance grows, we recommend one of the other "
"methods to maintain performance."
msgstr ""

#: ../settings/system/storage.rst:38
msgid "Filesystem"
msgstr ""

#: ../settings/system/storage.rst:22
msgid ""
"This storage method is recommended for all Zammad instances, especially for "
"those with a higher load. If you choose filesystem, your files are written "
"to ``/opt/zammad/storage/``."
msgstr ""

#: ../settings/system/storage.rst:26
msgid ""
"Moving attachments from \"Database\" to \"Filesystem\" can be run during "
"production use. However, you should consider your framework conditions (e.g. "
"bandwidth, system load in production) to define the right moment."
msgstr ""

#: ../settings/system/storage.rst:32
msgid "**You noticed slow updates of Zammad?**"
msgstr ""

#: ../settings/system/storage.rst:34
msgid ""
"While Zammad is beeing updated, it enforces a recursive \"change "
"owner\" (chown) for this directory. For instances with many files this can "
"be time consuming. To mitigate that you can move your files and create a "
"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have "
"to make sure on your own that the permissions are always correct."
msgstr ""

#: ../settings/system/storage.rst:95
msgid "Simple Storage (S3)"
msgstr ""

#: ../settings/system/storage.rst:41
msgid ""
"To use the Simple Storage (S3), you have to provide some settings, which "
"can't be accessed in the UI (see instructions below)."
msgstr ""

#: ../settings/system/storage.rst:44
msgid ""
"⚠️ Please note that the current implementation is in its early stages and can "
"be modified in the future."
msgstr ""

#: ../settings/system/storage.rst:47
msgid ""
"The prerequisite is to have access to a S3-compatible storage and to have "
"all necessary parameters available (which depends on your storage provider; "
"if in doubt, please ask there for help)."
msgstr ""

#: ../settings/system/storage.rst:51
msgid "Steps to configure S3:"
msgstr ""

#: ../settings/system/storage.rst:53
msgid ""
"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``"
msgstr ""

#: ../settings/system/storage.rst:54
msgid "Edit the copied file in one of the following ways:"
msgstr ""

#: ../settings/system/storage.rst:56
msgid ""
"Either provide your S3 configuration with one attribute per line like in the "
"upper area of the file"
msgstr ""

#: ../settings/system/storage.rst:58
msgid ""
"Or provide your S3 configuration as an URL (which you can find at the end of "
"the file). Note: you can also provide this URL as environment variable (:"
"docs:`see system documentation </appendix/configure-env-vars.html#storage-"
"options>`) without using this yml-file."
msgstr ""

#: ../settings/system/storage.rst:62
msgid ""
"We recommend the deletion of the not used configuration style to avoid "
"inconsistencies."
msgstr ""

#: ../settings/system/storage.rst:65
msgid "Restart Zammad so the config file / environment variable is loaded"
msgstr ""

#: ../settings/system/storage.rst:66
msgid ""
"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings "
"> System > Storage and click on \"Submit\". After that, Zammad checks your "
"configuration and the connection to the service and will raise an error "
"message if something is wrong."
msgstr ""

#: ../settings/system/storage.rst:72
msgid "A very simple storage configuration could look like this:"
msgstr ""

#: ../settings/system/storage.rst:85
msgid ""
"Before setting the storage method to ``Simple Storage (S3)`` (step 4), "
"please make sure to have a working setup."
msgstr ""

#: ../settings/system/storage.rst:88
msgid ""
"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); "
"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is "
"fine, you should see ``true``, else you should see ``false`` and a simple "
"error message."
msgstr ""

#: ../settings/system/storage.rst:93
msgid ""
"If you installed Zammad through a package manager (rather than from source), "
"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :"
"docs:`Administration via Console </admin/console.html>`."
msgstr ""

#: ../settings/ticket.rst:4
msgid ""
"Here you can adjust general ticket settings. Additional ones for the ticket "
"composer interface can be found in the :doc:`/misc/composer`."
msgstr ""

#: ../settings/ticket.rst:11
msgid "Ticket Hook (default: ``Ticket#``)"
msgstr ""

#: ../settings/ticket.rst:11
msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#."
msgstr ""

#: ../settings/ticket.rst:38
msgid "Ticket Hook Position (default: ``right``)"
msgstr ""

#: ../settings/ticket.rst:14
msgid ""
"With this setting you can decide (if) where to insert the ticket number."
msgstr ""

#: ../settings/ticket.rst:20
msgid "*Right*"
msgstr ""

#: ../settings/ticket.rst:17
msgid ""
"This setting will add the ticket reference on the right site of the subject."
msgstr ""

#: ../settings/ticket.rst:20
msgid "Example: ``Some Subject [Ticket#12345]``"
msgstr ""

#: ../settings/ticket.rst:26
msgid "*Left*"
msgstr ""

#: ../settings/ticket.rst:23
msgid ""
"This setting will add the ticket reference on the left site of the subject."
msgstr ""

#: ../settings/ticket.rst:26
msgid "Example: ``[Ticket#12345] Some Subject``"
msgstr ""

#: ../settings/ticket.rst:29
msgid "*None*"
msgstr ""

#: ../settings/ticket.rst:29
msgid "This will completely remove ticket references from the subject."
msgstr ""

#: ../settings/ticket.rst:33
msgid ""
"Please ensure to take a look at :doc:`/channels/email/settings` within the "
"email channel to ensure you have at least one reference that helps Zammad to "
"assign follow-ups correctly."
msgstr ""

#: ../settings/ticket.rst:37
msgid ""
"Disabling this and not setting up any further follow up search will lead to "
"unexpected results!"
msgstr ""

#: ../settings/ticket.rst:65
msgid ""
"Ticket Last Contact Behaviour (default: ``Use the start time of the last "
"customer thread (which may consist of multiple articles).``)"
msgstr ""

#: ../settings/ticket.rst:41
msgid ""
"This setting changes the way Zammad updates the ``Last Contact`` value of a "
"ticket. This is fairly important for overviews and what you expect upon "
"ticket updates of a customer."
msgstr ""

#: ../settings/ticket.rst:52
msgid ""
"Use the start time of the last customer thread (which may consist of "
"multiple articles)."
msgstr ""

#: ../settings/ticket.rst:46
msgid ""
"If this option is chosen, Zammad will update the last updated value just "
"once if a customer replies. After that, Zammad will wait for an agent to "
"react."
msgstr ""

#: ../settings/ticket.rst:50
msgid ""
"This comes in handy if you want to work tickets in the order of their first "
"update. This will not change ticket orders if customers decide to \"bump\" "
"the ticket affected."
msgstr ""

#: ../settings/ticket.rst:57
msgid "Use the time of the very last customer article."
msgstr ""

#: ../settings/ticket.rst:55
msgid ""
"When setting this option, Zammad will always update the last updated value. "
"This means that if ordering by ``Last Update``, ticket orders will change if "
"customers \"bump\" the ticket."
msgstr ""

#: ../settings/ticket.rst:64
msgid "Last contact value used on :doc:`/manage/overviews`"
msgstr ""

#: ../settings/ticket.rst:65
msgid "Last contact value used on :doc:`/manage/trigger`"
msgstr ""

#: ../settings/ticket.rst:88
msgid ""
"Ticket Organization Reassignment (default: ``Update the most recent tickets."
"``)"
msgstr ""

#: ../settings/ticket.rst:68
msgid ""
"This setting changes the way Zammad updates the organization field of the "
"tickets whenever the primary organization of a user is changed."
msgstr ""

#: ../settings/ticket.rst:74
msgid "Update the most recent tickets."
msgstr ""

#: ../settings/ticket.rst:72
msgid ""
"If this option is chosen, Zammad will update the 100 most recent tickets "
"where the user is the ticket customer. The ticket organization field will be "
"automatically set to the new primary organization of the user."
msgstr ""

#: ../settings/ticket.rst:88
msgid "Do not update any tickets."
msgstr ""

#: ../settings/ticket.rst:77
msgid ""
"When choosing this option, Zammad will not update any tickets when the "
"user's primary organization is changed."
msgstr ""

#: ../settings/ticket.rst:80
msgid "**Use with care!**"
msgstr ""

#: ../settings/ticket.rst:82
msgid ""
"Using this option may lead to inconsistencies in the system as the ticket "
"organization may become decoupled from the ticket customer."
msgstr ""

#: ../settings/ticket.rst:85
msgid ""
"However, you may use this option if you wish to maintain :ref:`the shared "
"access <organization-details-reference>` to the ticket for all organization "
"members of the original organization of the customer."
msgstr ""

#: ../settings/ticket.rst:110
msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)"
msgstr ""

#: ../settings/ticket.rst:94
msgid ""
"This setting defines the way Zammad's ticket number will look. Changing this "
"setting in production will cause follow up detection to fail."
msgstr ""

#: ../settings/ticket.rst:102
msgid "Increment (SystemID.Counter)"
msgstr ""

#: ../settings/ticket.rst:98
msgid ""
"The increment value contains the SystemID (automatically generated during "
"installation) and a increment which counts up with every new Ticket. The "
"increment will automatically get another digit if needed."
msgstr ""

#: ../settings/ticket.rst:102
msgid "Examples: ``1010138``, ``1010139``"
msgstr ""

#: ../settings/ticket.rst:110
msgid "Date (Year.Month.Day.SystemID.Counter)"
msgstr ""

#: ../settings/ticket.rst:105
msgid ""
"This version of the ticket number is fairly long. However, because it "
"contains the date of ticket creation, it also allows you to see when the "
"ticket has been created. You may feel familiar with this number format if "
"you've worked with OTRS already."
msgstr ""

#: ../settings/ticket.rst:110
msgid "Examples: ``201206231010138``, ``201206231010139``"
msgstr ""

#: ../settings/ticket.rst:137
msgid "OPTIONS"
msgstr ""

#: ../settings/ticket.rst:113
msgid ""
"The below options allow you to further customize your ticket number. The "
"availability of options differ depending of the chosen ticket number format "
"above."
msgstr ""

#: ../settings/ticket.rst:122
msgid "Checksum (default: ``no``)"
msgstr ""

#: ../settings/ticket.rst:118
msgid ""
"If set to yes, we'll built a checksum to further \"unique\" the ticket "
"number of your system. If you're dealing with many other ticket systems this "
"might help to prevent false positive follow up detection on tickets."
msgstr ""

#: ../settings/ticket.rst:122
msgid "This will also add another digit to the ticket number."
msgstr ""

#: ../settings/ticket.rst:137
msgid "Min. size of Number (default: ``5``)"
msgstr ""

#: ../settings/ticket.rst:125
msgid ""
"This setting defines the minimum length of your ticket number. If your "
"counter is not yet high enough, Zammad will fill the number with zeros to "
"ensure the wanted length."
msgstr ""

#: ../settings/ticket.rst:129
msgid ""
"Please note that the minimum length is ``3`` (SystemID + at least one digit "
"if below 10). Also, if the length is no longer long enough, the number will "
"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus "
"it's save to keep it at 5 or set it lower if wanted."
msgstr ""

#: ../settings/ticket.rst:135
msgid ""
"This option is only available if ticket number format is set to "
"``Increment``!"
msgstr ""

#: ../settings/ticket.rst:142
msgid "Auto-Assignment"
msgstr ""

#: ../settings/ticket.rst:144
msgid ""
"In a larger Zammad environment, it happens that several agents open the same "
"ticket at the same time. Although collision detection is then effective, the "
"efficiency of processing can be increased by means of the automatic "
"assignment of tickets when a ticket is opened."
msgstr ""

#: ../settings/ticket.rst:149
msgid ""
"The automatic assignment of tickets can be activated and configured in the "
"admin area under Settings > Ticket > Auto Assignment."
msgstr ""

#: ../settings/ticket.rst:152
msgid ""
"The auto assignment only works if the ticket has no owner yet. By default, "
"the agent can always reset the ticket owner to ``-`` if needed."
msgstr ""

#: ../settings/ticket.rst:155
msgid ""
"If you want to use this function for only specific tickets, you can "
"configure the conditions accordingly to meet your requirement. By default "
"the condition affects all tickets with the state ``open``."
msgstr ""

#: ../settings/ticket.rst:161
msgid ""
"If you need to exclude users (e.g. a group leader), you can search and "
"select the desired agents in the ``Exception Users`` list. The search "
"function in this area is only effective, if you have too many agents to "
"display at once to help you with the configuration."
msgstr ""

#: ../settings/ticket.rst:167
msgid "Language Detection"
msgstr ""

#: ../settings/ticket.rst:169
msgid ""
"Zammad offers a built in language detection for articles. By default, it is "
"turned off. Turn it on by selecting a backend service and confirm by "
"clicking **Submit**."
msgstr ""

#: ../settings/ticket.rst:173
msgid ""
"After enabling it, Zammad tries to detect the language of each **new** "
"article. The language is not detected for existing articles."
msgstr ""

#: ../settings/ticket.rst:177
msgid ""
"Currently, there is only one backend service available: `Compact Language "
"Detection <https://github.com/jtoy/cld>`_."
msgstr ""

#: ../settings/ticket.rst:179
msgid ""
"Be aware that this feature is in its early stages. Enhancements may come in "
"very soon."
msgstr ""

#: ../settings/ticket.rst:181
msgid "While we noticed it works pretty well, it may fail for some edge cases."
msgstr ""

#: ../settings/ticket.rst:182
msgid ""
"The language selection in conditions and the output in the article detail "
"view is always in English. The language names are not translated into user's "
"current language."
msgstr ""

#: ../settings/ticket.rst:186
msgid ""
"You can see the name of the detected language in the detail view of an "
"article. You can display additional information by clicking on an article, "
"which expands more details:"
msgstr ""

#: ../settings/ticket.rst:None
msgid "Screenshot showing detected language in article detail view"
msgstr ""

#: ../settings/ticket.rst:194
msgid "If you are wondering what this feature is useful for, the answer is:"
msgstr ""

#: ../settings/ticket.rst:196
msgid ""
"Use the detected language as a condition attribute in triggers and "
"schedulers. Examples are: to send auto replies in different languages (see :"
"ref:`trigger example <trigger-example-3>`) and to move tickets in a specific "
"language into a specific group."
msgstr ""

#: ../settings/ticket.rst:200
msgid ""
"Search by the new article attribute in the advanced search (both via "
"language code and language name). Examples: ``article.detected_language:"
"en``, ``article.detected_language_name:english``"
msgstr ""

#: ../settings/ticket.rst:205
msgid "Notifications"
msgstr ""

#: ../settings/ticket.rst:229
msgid "Default Notifications"
msgstr ""

#: ../settings/ticket.rst:208
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:213
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:219
msgid ""
"**Potential time-consuming action:** Applying default ticket notifications "
"to all agent users may take some time to complete, be patient! The exact "
"time will depend on the size of your system and the number of agents."
msgstr ""

#: ../settings/ticket.rst:223
msgid ""
"**Active agents only!** When current default ticket notifications are "
"applied, only active agent users are considered. In case an agent is re-"
"activated *after* this action, they will still have the old notification "
"configuration."
msgstr ""

#: ../settings/ticket.rst:228
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:234
msgid "Duplicate Detection"
msgstr ""

#: ../settings/ticket.rst:276
msgid "Detect Duplicate Ticket Creation"
msgstr ""

#: ../settings/ticket.rst:237
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:244
msgid "A Sample Duplicate Ticket Warning"
msgstr ""

#: ../settings/ticket.rst:246
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:251
msgid "**Warning title** and **Warning message** are configurable as well."
msgstr ""

#: ../settings/ticket.rst:253
msgid ""
"You can limit the detection only to certain user roles. By default, only "
"agents will see the warning."
msgstr ""

#: ../settings/ticket.rst:256
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:259
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:265
msgid "**🦺 Safety first!**"
msgstr ""

#: ../settings/ticket.rst:267
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:271
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:275
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 adjust object attributes in many ways. For "
"example:"
msgstr ""

#: ../system/core-workflows.rst:7
msgid "show / hide fields"
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 can provide exactly the information your users 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 <core-workflow-ajax-mode>`"
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/condition-operators.rst:2
msgid "Core Workflow Condition Operators"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:4
msgid ""
"You might know that there is a separate section for explaining :doc:"
"`condition operators </misc/object-conditions/basics>`. Head over there to "
"see a detailed explanation of many conditions and operators."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:8
msgid ""
"Due to differences to other places in Zammad which are also using conditions "
"(e.g. triggers), you can find a dedicated description of operators for core "
"workflows below."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:12
msgid ""
"Be aware that the availability of the operators depends on the selected "
"attribute and its field type. Some of the operators may only be available "
"for system attributes (e.g. for \"tags\", \"active\")."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:20
msgid "Operator"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:22
msgid "after (absolute)"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:23
msgid "Matches if a date/time is after a specific point in time."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:24
msgid "after (relative)"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:25
msgid "Matches if a time span after a specified event has passed."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:26
msgid "before (absolute)"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:27
msgid "Matches if a date/time is before a specific point in time."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:28
msgid "before (relative)"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:29
msgid "Matches if a time span after a specified event has not passed."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:30
msgid "contains"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:31
msgid "Matches if a specified value is present."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:33
msgid "Matches if all of the specified values are present."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:35
msgid "Matches if none of the specified values are present."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:36
msgid "contains not"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:37
msgid "Matches if a specified value is not present."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:39
msgid "Matches if one specified value is present."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:41
msgid "Matches if one specified value is not present."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:42
msgid "does not match regex"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:43
msgid "Matches if content doesn't fit to regex rule."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:44
msgid "ends with"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:45
msgid "Matches if content ends with specified value."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:46
msgid "ends with one of"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:47
msgid "Matches if content ends with one of the specified values."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:48
msgid "from (relative)"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:49
msgid "Matches if date/time is after a period of time after an event."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:51
msgid "Matches if content is equal to a specified value."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:52
msgid "is any of"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:53
msgid "Matches if content is equal to any of specified values."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:54
msgid "is modified"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:55
msgid "Matches if content is modified."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:57
#: ../system/core-workflows/condition-operators.rst:61
msgid "True from the moment of changing content until form submit."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:58
msgid "is modified to"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:59
msgid "Matches if content is modified to a specific value."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:62
msgid "is none of"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:63
msgid "Matches if content is none of any specified values."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:65
msgid "Matches if content is not equal to a specified value."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:67
msgid "Matches if content is present."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:68
msgid "just changed"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:69
msgid "Matches if content has changed."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:71
#: ../system/core-workflows/condition-operators.rst:75
msgid ""
"Only true for the moment of changing content until next form field action/"
"click."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:72
msgid "just changed to"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:73
msgid "Matches if content has changed to a specified value."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:76
msgid "matches regex"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:77
msgid "Matches if value fits to regex rule."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:79
msgid "Matches if no content is present."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:80
msgid "starts with"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:81
msgid "Matches if content starts with specified value."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:82
msgid "starts with one of"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:83
msgid "Matches if content starts with one of the specified values."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:84
msgid "till (relative)"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:85
msgid "Matches if date/time is before a period of time before an event."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:86
msgid "today"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:87
msgid "Matches if date/time is today."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:88
msgid "within last (relative)"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:89
msgid ""
"Matches if date/time content is within specified period of time before now."
msgstr ""

#: ../system/core-workflows/condition-operators.rst:91
msgid "within next (relative)"
msgstr ""

#: ../system/core-workflows/condition-operators.rst:92
msgid ""
"Matches if date/time content is within specified period of time after now."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:2
msgid "How do they work?"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:4
msgid ""
"Core Workflows are executed according to their priority. If two workflows "
"have the same priority, they are executed in alphabetical order based on "
"their **name**."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:8
msgid ""
"Because of the way Core Workflows work, all changes to attributes are "
"checked with the application server - please see :doc:`limitations` for "
"possible issues."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:12
msgid ""
"Below we're talking about settings that are important and not self-"
"explanatory."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:17
msgid ""
"Choose the object context you want to run the workflow in. This will decide "
"on your available attributes and actions."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:20
msgid "Ticket objects also have access to the ticket customer."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:25
msgid ""
"Choose in which situation the workflow is applied. Contexts can be combined "
"to avoid duplicate workflows."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:30
msgid "Creation mask"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:29
msgid ""
"If selected, your conditions and actions will affect all applicable creation "
"masks."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:34
msgid "Edit mask"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:33
msgid ""
"If selected, your conditions and actions will affect all applicable edit "
"masks."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:39
msgid ""
"Zammad differentiates between selected and saved conditions. These can be "
"combined wherever needed."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:42
msgid "**⚠️ Restrict workflows to specific roles if needed!**"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:44
msgid ""
"By default and unless configured in conditions, workflow rules are executed "
"for **all roles**. This also affects your customers!"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:50
msgid "Selected Conditions"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:48
msgid ""
"These conditions are based on form values and match if an appropriate "
"selection is made (e.g. choosing another group in the ticket without "
"saving). This applies for drafts (active selection) and currently saved "
"values."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:64
msgid "Saved Conditions"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:53
msgid ""
"These conditions only match if the selected values are stored in the "
"database. It ignores the current value or selection of the field, as long as "
"the changes are not saved (e.g. performing field operations for an existing "
"ticket, which is viewed/opened by an agent)."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:60
msgid ""
"Keep in mind that the value has to be available in the situation where you "
"need it. Otherwise the condition won't match."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:63
msgid ""
"Example: you can't perform any actions with *saved condition* on a ticket in "
"creation, because there are no saved values at that time."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:66
msgid ""
"You can find a description of the condition operators for core workflows :"
"doc:`here </system/core-workflows/condition-operators>`."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:72
msgid ""
"Which actions should we run on the relevant fields? The possible actions "
"depend on the object type. However, usually you can at least change the "
"visibility and whether the field is mandatory."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:76
msgid "Be aware that actions are not available for **related** context."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:78
msgid ""
"**Example:** Let's assume you are working in the ticket context. While you "
"can have customer *conditions*, you *can't adjust* objects with actions in "
"that scope. That's because this wouldn't have any impact on the ticket "
"dialog. Of course all ticket attributes (state, owner, ...) are available."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:84
msgid ""
"Please also have a look at our :doc:`limitations` to be safe from surprises."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:88
msgid "Available Operators"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:90
msgid "The availability of operators depends on the object type and scope."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:94
msgid ""
"Please note that actions may or may not restrict API based access to "
"attributes. We're displaying the following icons for your overview to "
"understand these limits better:"
msgstr ""

#: ../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:163
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:167
msgid "ui"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:102
msgid "show |ui|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:102
msgid "Display the chosen field. Allows setting of values."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:109
msgid "hide |ui|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:105
msgid ""
"Hide the chosen field. However, it technically still allows setting the "
"field."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:108
msgid ""
"Please note that the field is **not** gone and still contains an existing "
"value (if set)! Consider *remove* instead, if you want this field to be gone."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:112
msgid "remove |ui|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:112
msgid "Entirely removes the field. The field value will not be evaluated."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:115
msgid "set mandatory |ui| |api|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:115
msgid "Sets the field to mandatory."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:118
msgid "set optional |ui| |api|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:118
msgid "Sets the field to optional."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:124
msgid "add option |ui| |api|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:121
msgid "Allows adding options to tree selects or selects."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:123
msgid ""
"You have to use the \"remove option\" before performing this action. It "
"allows you to use *existing* configured values."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:128
msgid "remove option |ui| |api|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:127
msgid ""
"Allows removing options from tree selects or selects. It allows you to use "
"*existing* configured values."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:134
msgid "set fixed to |ui| |api|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:131
msgid "Reduces the available options by your selection."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:133
msgid ""
"This reduces your workflows in terms of *add option* and *remove option*."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:137
msgid "fill in |ui|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:137
msgid "Allows filling in of string and integer fields with your values."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:141
msgid "fill in empty |ui|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:140
msgid ""
"Allows filling in of string and integer fields with your values **if the "
"field is empty**."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:144
msgid "select |ui|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:144
msgid "Select a specific value within a select, tree select or boolean field."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:153
msgid "auto select |ui|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:147
msgid "Helps users with tree select and select fields:"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:149
msgid ""
"If the field has only one option available for selection and no value yet, "
"the value will be automatically set."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:152
msgid ""
"This option only works if you have one value and doesn't work if there is "
"more than one option available."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:157
msgid "set readonly |ui|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:156
msgid ""
"Allows you to display an attribute as read only (which means no changes are "
"possible)."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:161
msgid "unset readonly |ui|"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:160
msgid ""
"In case a workflow set the field in question to read only, you can undo this "
"with option above."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:172
msgid "Stop after match"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:174
msgid ""
"Here you can decide if other workflows are executed after the current one."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:176
msgid ""
"If set to ``no`` (default), further workflows will be executed if they match "
"the condition. In this case, it is possible that your actions from the "
"current workflow can be overwritten by another workflow."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:180
msgid ""
"If set to ``yes``, no further worflows will be executed after the current "
"one."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:184
msgid "Priority"
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:186
msgid ""
"You can define the sequence, in which the workflows are executed. The "
"default value is ``500``."
msgstr ""

#: ../system/core-workflows/how-do-they-work.rst:189
msgid ""
"The workflows are executed in ascending order by their priority. That means "
"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)."
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:2
msgid "Learn by Example"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:4
msgid ""
"This page provides some basic examples for Core Workflows. Of course you can "
"build much more complex workflows if needed."
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:7
msgid ""
"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`."
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:10
msgid "Group Based Examples"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:12
msgid ""
"All following workflows have the same base configurations. The workflow may "
"not use them all."
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:15
msgid "Groups:"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:20
msgid "Attributes:"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:22
msgid "Category (Single tree selection field, not mandatory, agents only)"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:23
msgid ""
"Approved (Boolean field, not mandatory, not shown, ``false`` as default)"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:24
msgid "Operating System (Text field, not mandatory, not shown)"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:25
msgid "Software used (Single selection field, not mandatory, not shown)"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:68
msgid "Group specific values and fields"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:28
msgid ""
"This workflow set depends on the category field. It reduces the available "
"set of values based on the group selected."
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:33
msgid "Workflow 2nd Level group"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:35
msgid ""
"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and "
"``Others``. It also sets further required fields to mandatory and visible."
msgstr ""

#: ../system/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:43
msgid "Workflow Support group"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:45
msgid ""
"This reduces the category options to ``Support/*``, ``Internal/*`` and "
"``Others``. It also sets further required fields to visible."
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:53
msgid "Workflow Sales group"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:55
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:68
#: ../system/integrations/slack.rst:88
msgid "The Result"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:63
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:90
msgid "Approval process"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:71
msgid ""
"In this case ``approved`` is visible to agents by default. For this "
"workflow, an additional role ``Approval person`` is required (no further "
"permissions)."
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:81
msgid ""
"This workflow may work best in combination with a :doc:`trigger </manage/"
"trigger>` but technically, this is not required."
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:84
msgid ""
"Select fields may be a better approach because they allow more values than "
"just a simple ``true`` or ``false``."
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:103
msgid "State dependent mandatory fields"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:93
msgid ""
"This workflow sets ``Category`` to mandatory if the agent wants to set the "
"states ``closed`` or ``pending close`` to enforce categorization."
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/learn-by-example.rst:106
msgid "Manual Ticket Handover Process"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:108
msgid "This example covers the handover of a ticket from one agent to another:"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:110
msgid ""
"When the ticket owner is modified, a new text field (\"Handover\") shows up "
"for a comment"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:112
msgid ""
"This may only be visible when the owner is changed, therefore it has to be "
"hidden in general"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:114
msgid "The input in this handover text field is mandatory"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:115
msgid ""
"After submitting changes, the value of the handover field must be added as "
"an note to the ticket (via trigger)"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:121
msgid "Hiding handover field"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:0
msgid "Hiding the handover field in core workflows"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:126
msgid "Showing handover field and setting it to mandatory"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:0
msgid "Showing the handover field and set it as mandatory"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:131
msgid "Trigger writing handover input to a new article"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:0
msgid "Write handover content to a new article"
msgstr ""

#: ../system/core-workflows/learn-by-example.rst:133
msgid ""
"As a result, the ticket includes an article of the type note which includes "
"the predefined text and the handover comment."
msgstr ""

#: ../system/core-workflows/limitations.rst:6
msgid "Core Workflows do not replace Triggers"
msgstr ""

#: ../system/core-workflows/limitations.rst:5
msgid ""
"Workflows manipulate the behavior of fields. However, they do not set values "
"in fields because of actions."
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:25
msgid "Some fields stay unavailable to customers"
msgstr ""

#: ../system/core-workflows/limitations.rst:19
msgid ""
"For technical and security reasons, some default fields (the pale ones you "
"can't edit) stay unavailable for display and usage on customer permissions."
msgstr ""

#: ../system/core-workflows/limitations.rst:23
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:29
msgid "Ticket title changes not supported in edit mask"
msgstr ""

#: ../system/core-workflows/limitations.rst:28
msgid ""
"It is currently not possible to perform changes of the ticket title in the "
"edit mask (e.g. renaming, set to read-only)."
msgstr ""

#: ../system/core-workflows/limitations.rst:37
msgid "What is out of scope of Core Workflows?"
msgstr ""

#: ../system/core-workflows/limitations.rst:32
msgid ""
"There are some things that would count as workflow but are either done via :"
"doc:`/manage/trigger` or :doc:`/manage/scheduler`."
msgstr ""

#: ../system/core-workflows/limitations.rst:35
msgid "Such as (but not limited to):"
msgstr ""

#: ../system/core-workflows/limitations.rst:37
msgid "up- or downgrade permissions of users"
msgstr ""

#: ../system/core-workflows/limitations.rst:38
msgid "affecting article creation or listing"
msgstr ""

#: ../system/data-privacy.rst:2
msgid "Data Privacy"
msgstr ""

#: ../system/data-privacy.rst:4
msgid ""
"For 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:8
msgid ""
"You can create manual deletion tasks or even automated deletion tasks for "
"tickets and users based on custom conditions via :doc:`scheduler </manage/"
"scheduler>`!"
msgstr ""

#: ../system/data-privacy.rst:12
msgid ""
"Access to this panel requires ``admin.data_privacy`` permissions (introduced "
"in Zammad 3.5)."
msgstr ""

#: ../system/data-privacy.rst:15
msgid ""
"On older systems that have not been updated yet, customers can also be :docs:"
"`deleted via the Zammad console </admin/console/dangerzone-for-experts."
"html#deleting-customers>`."
msgstr ""

#: ../system/data-privacy.rst:22
msgid "User deletion dialog in the Data Privacy panel"
msgstr ""

#: ../system/data-privacy.rst:22
msgid ""
"The user deletion dialog lists some of the tickets that will be removed from "
"the system along with the user."
msgstr ""

#: ../system/data-privacy.rst:27
msgid "Deleting Users via GUI"
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 canceled 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:51
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:51
msgid "Click **Action > Delete**."
msgstr ""

#: ../system/data-privacy.rst:58
msgid "**in the “Manage > Users” Admin Panel**"
msgstr ""

#: ../system/data-privacy.rst:0
msgid "Accessing the user deletion dialog under “Users” in the Admin Panel"
msgstr ""

#: ../system/data-privacy.rst:58
msgid "Use the **⋮ Actions** menu for the target user."
msgstr ""

#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104
msgid "**in the “System > Data Privacy” Admin Panel**"
msgstr ""

#: ../system/data-privacy.rst:0
msgid ""
"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel"
msgstr ""

#: ../system/data-privacy.rst:65
msgid ""
"Use the **New Deletion Task** button. Search for users by name or email "
"address."
msgstr ""

#: ../system/data-privacy.rst:79
msgid "**Delete organizations**"
msgstr ""

#: ../system/data-privacy.rst:69
msgid ""
"If the customer you are deleting is the last user in their organization, a "
"**Delete Organization?** option will be displayed in the user deletion "
"dialog:"
msgstr ""

#: ../system/data-privacy.rst:0
msgid "Deleting an organization via the user deletion dialog"
msgstr ""

#: ../system/data-privacy.rst:78
msgid ""
"If this option does not appear, make sure there are no pending deletion "
"tasks for other customers from this organization."
msgstr ""

#: ../system/data-privacy.rst:82
msgid "Step 2: Monitor Deletion Job Status"
msgstr ""

#: ../system/data-privacy.rst:84
msgid ""
"It may take up to ten minutes for the system to process your request, so for "
"each user you delete, a “deletion task” is added to the queue. You can keep "
"an eye on the status of these tasks in two places:"
msgstr ""

#: ../system/data-privacy.rst:98
msgid "**in the Activity Stream**"
msgstr ""

#: ../system/data-privacy.rst:0
msgid "Activity Stream showing data privacy tasks"
msgstr ""

#: ../system/data-privacy.rst:94
msgid ""
"For each deleted user, the Activity Stream will be updated twice—once when "
"the task is created, and once when it's complete."
msgstr ""

#: ../system/data-privacy.rst:97
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:107
msgid "Frequently Asked Questions"
msgstr ""

#: ../system/data-privacy.rst:121
msgid "What happens if I receive an email from a deleted customer?"
msgstr ""

#: ../system/data-privacy.rst:110
msgid ""
"Zammad automatically creates a new user account whenever it receives a "
"message from an unrecognized email address, including deleted users. Deleted "
"users are never blocked from creating new tickets."
msgstr ""

#: ../system/data-privacy.rst:115
msgid ""
"In the unlikely event that you receive an email between the time that you "
"click “Delete” and the system has processed your request, **that ticket will "
"be automatically removed**. The ticket number for the lost ticket will be "
"displayed in the Admin Panel under **System > Data Privacy > Completed Tasks "
"> Delete User > Deleted Tickets**."
msgstr ""

#: ../system/data-privacy.rst:130
msgid "What about user information stored in internal notes or other messages?"
msgstr ""

#: ../system/data-privacy.rst:124
msgid ""
"The deletion process removes **user accounts and associated tickets only**."
msgstr ""

#: ../system/data-privacy.rst:126
msgid ""
"If there are references to a user's name or information stored elsewhere in "
"the system, that information **will not be removed** because there is no way "
"to safely determine if it actually describes the user in question."
msgstr ""

#: ../system/data-privacy.rst:137
msgid "I deleted an user and can still see a message they sent!"
msgstr ""

#: ../system/data-privacy.rst:133
msgid ""
"Tickets can only belong to a single customer, but may contain messages "
"(“articles”) from many people. If you deleted a user but you're still seeing "
"articles they sent, don't worry—those articles are for a ticket that belongs "
"to someone else, and no longer contain any reference to the sender's "
"identity."
msgstr ""

#: ../system/data-privacy.rst:141
msgid "I removed a customer, now my reporting is off!"
msgstr ""

#: ../system/data-privacy.rst:140
msgid ""
"When removing users and their tickets, all references are removed. This also "
"affects e.g. Reporting - these information are lost."
msgstr ""

#: ../system/data-privacy.rst:145
msgid "How long does Zammad store created tasks?"
msgstr ""

#: ../system/data-privacy.rst:144
msgid ""
"Please see the on-premise data section of the :docs:`data privacy </appendix/"
"privacy.html>` chapter."
msgstr ""

#: ../system/data-privacy.rst:150
msgid "What about re-assigned tickets? I want to delete them, too."
msgstr ""

#: ../system/data-privacy.rst:148
msgid ""
"Only tickets assigned to the matching customer at the time of the execution "
"of the data privacy deletion task will be deleted. The deletion will not "
"consider historical assignments."
msgstr ""

#: ../system/data-privacy.rst:154
msgid "Why are there so many deletion task entries, I didn't create them!"
msgstr ""

#: ../system/data-privacy.rst:153
msgid ""
"The deletion tasks can come from the :doc:`/manage/scheduler` as well. "
"Namely the action *\"Add a data privacy deletion task\"* is causing the "
"entries."
msgstr ""

#: ../system/integrations/checkmk/admin-panel-reference.rst:2
msgid "Admin Panel Reference"
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 </manage/groups/index>` 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 <checkmk-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 can choose from the seven built-in ticket states. If these states aren't "
"enough for you, you can :ref:`define a new ticket state <ticket-state-"
"reference>` for this purpose as well. This can be useful for tracking "
"tickets with :doc:`reports </manage/report-profiles>`, for example."
msgstr ""

#: ../system/integrations/checkmk/admin-panel-reference.rst:35
#: ../system/integrations/cti/includes/recent-logs.include.rst:2
#: ../system/integrations/ldap/index.rst:74
#: ../system/integrations/pgp/index.rst:106
msgid "Recent Logs"
msgstr ""

#: ../system/integrations/checkmk/admin-panel-reference.rst:None
msgid "Screenshot of Checkmk \"Recent Logs\" section"
msgstr ""

#: ../system/integrations/checkmk/admin-panel-reference.rst:41
msgid ""
"If you're having trouble getting Zammad and Checkmk to play nicely together, "
"this section can help you troubleshoot."
msgstr ""

#: ../system/integrations/checkmk/admin-panel-reference.rst:44
msgid ""
"It contains a record of the fifty most recent transactions that Zammad knows "
"about, including each one's request/response details and return status."
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 <checkmk-api-"
"alerts>` 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: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:32
msgid "How Does it Work?"
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:52
msgid "Ticket attributes"
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 (“<host> is <state>”)."
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 (“<host> is "
"<state>”)."
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: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: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 </system/objects>`."
msgstr ""

#: ../system/integrations/checkmk/api-reference.rst:145
msgid "Please note that the following attributes are **not customizable**:"
msgstr ""

#: ../system/integrations/checkmk/api-reference.rst:147
msgid "title"
msgstr ""

#: ../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: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 "Which Values Can Be Set?"
msgstr ""

#: ../system/integrations/checkmk/api-reference.rst:157
msgid "😵 **Invalid values → unpredictable behavior**"
msgstr ""

#: ../system/integrations/checkmk/api-reference.rst:159
msgid ""
"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 <checkmk-parameter-state>`."
msgstr ""

#: ../system/integrations/checkmk/api-reference.rst:222
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 :docs:"
"`rails console </admin/console.html>`. Valid values are those that you can "
"set with a string:"
msgstr ""

#: ../system/integrations/checkmk/api-reference.rst:218
msgid "These values can then be passed directly to the API:"
msgstr ""

#: ../system/integrations/checkmk/index.rst:16
msgid "How does it work?"
msgstr ""

#: ../system/integrations/checkmk/index.rst:2
msgid "Checkmk"
msgstr ""

#: ../system/integrations/checkmk/index.rst:4
msgid ""
"`Checkmk <https://checkmk.com/>`_ is a powerful IT monitoring tool that can "
"send real-time status alerts to Zammad via email or REST API. Set these "
"alerts up in Checkmk, and Zammad will automatically create, update, and "
"close tickets based on the health of your system:"
msgstr ""

#: ../system/integrations/checkmk/index.rst:14
msgid "Screenshot of ticket created by Checkmk notifications"
msgstr ""

#: ../system/integrations/checkmk/index.rst:14
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 <https://checkmk.com/"
"cms_notifications.html>`_ for help with that)."
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:17
msgid ""
"As part of this new rule, you'll have to choose a **notification method** "
"(*i.e.,* a script to execute whenever the rule is triggered). This script "
"will be written by you (samples below), and contain the logic for sending "
"API/email messages to Zammad:"
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:26
msgid "Checkmk \"New Rule\" dialog"
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:26
msgid ""
"Find your custom scripts in the Checkmk WATO under **Notifications > New "
"Rule > Notification Method**."
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:29
msgid ""
"Once you're done setting up your new rule, you're all set! New tickets "
"should start coming in and auto-updating any time your rule is triggered."
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:33
msgid ""
"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-"
"logs`.)"
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:38
msgid "API Alerts"
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:40
msgid ""
"To add these scripts in the Checkmk WATO, copy them into your Checkmk "
"installation directory and make them executable. (Be sure to replace the "
"``zammad.example.com`` callback URL with the one found in your admin panel.)"
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:60
msgid "Service notification"
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:46
msgid ""
"For updates on the status of the software running on your server (*e.g.,* "
"postgres)."
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:75
msgid "Host notification"
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:63
msgid "For updates on the status of the server itself."
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:77
msgid "🤔 **What's with all the env vars?**"
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:79
msgid ""
"Whenever Checkmk runs these scripts, it needs to provide some information "
"about the event that triggered the notification. This information is passed "
"in the form of these ``$NOTIFY_*`` environment variables."
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:85
msgid ""
"You can specify additional parameters to pass to the script when you're "
"setting up your notification rule, but the ones you see here are all "
"provided by default."
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:90
msgid "Email Alerts"
msgstr ""

#: ../system/integrations/checkmk/setup-guide.rst:94
msgid ""
"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. "
"This section will be completed once they have been resolved. (Learn more at "
"GitHub issues `#2377 <https://github.com/zammad/zammad/issues/2377>`_ & "
"`#2180 <https://github.com/zammad/zammad/issues/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: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 <https://dashboard.clearbit.com/docs#enrichment-api>`_."
msgstr ""

#: ../system/integrations/clearbit.rst:62
msgid ""
"If you're happy with the above chosen Settings and your mapping, just save "
"the changes and enable Clearbit integration. Zammad will now start polling "
"the Clearbit API as users contact you."
msgstr ""

#: ../system/integrations/clearbit.rst:68
msgid ""
"Zammad does not synchronize with Clearbit on a regular basis, but on demand "
"if needed. This saves API calls."
msgstr ""

#: ../system/integrations/clearbit.rst:73
msgid ""
"Below the Settings and Mappings, you'll find our Integration log. You can "
"see what requests Zammad sent to Clearbit and also the APIs Response."
msgstr ""

#: ../system/integrations/clearbit.rst:78
msgid ""
"By the way, you can also view the API log on the Clearbit website - the "
"information seen is basically the same."
msgstr ""

#: ../system/integrations/clearbit.rst:84
msgid "Example When Adding a User"
msgstr ""

#: ../system/integrations/clearbit.rst:86
msgid ""
"To show you how fast information is added, we added a small Screencast "
"below. This shows the creation of the User Alex from Clearbit. As we already "
"set the last name of Alex to \"X\", Zammad did not update it. What Zammad "
"did was to add further information it received from Clearbit."
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 dialog or the user profile."
msgstr ""

#: ../system/integrations/cti/includes/introduction.include.rst:6
msgid ""
"Click the toggle next to the heading to activate or deactivate this "
"integration."
msgstr ""

#: ../system/integrations/cti/includes/introduction.include.rst:9
msgid ""
"If you want to learn more on how your agents can use this function, please "
"refer the :user-docs:`user documentation </extras/caller-log.html>`."
msgstr ""

#: ../system/integrations/cti/includes/introduction.include.rst:14
msgid ""
"Automatically opening new ticket dialogues or user profiles requires agent "
"to extension mapping - see more below."
msgstr ""

#: ../system/integrations/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 :docs:`CTI-API documentation </api/"
"generic-cti/index.html>`."
msgstr ""

#: ../system/integrations/cti/generic.rst:22
#: ../system/integrations/cti/placetel.rst:27
#: ../system/integrations/cti/sipgate.rst:30
msgid "Available Settings"
msgstr ""

#: ../system/integrations/cti/generic.rst:29
#: ../system/integrations/cti/placetel.rst:41
#: ../system/integrations/cti/sipgate.rst:40
msgid "Endpoint Settings"
msgstr ""

#: ../system/integrations/cti/generic.rst:25
msgid ""
"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:28
msgid ""
"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API "
"documentation </api/generic-cti/index.html>`."
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:43
#: ../system/integrations/cti/placetel.rst:49
#: ../system/integrations/cti/sipgate.rst:52
msgid "Call Settings"
msgstr ""

#: ../system/integrations/cti/generic.rst:39
#: ../system/integrations/cti/placetel.rst:49
#: ../system/integrations/cti/sipgate.rst:37
#: ../system/integrations/cti/sipgate.rst:50
msgid "Inbound"
msgstr ""

#: ../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:11
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:8
msgid ""
"Your telephony system has to support this function. Zammad will send a "
"``reject`` response which will cause your telephony system to hang up the "
"call. To callers this usually will feel like the line is busy."
msgstr ""

#: ../system/integrations/cti/includes/inbound-calls.include.rst:14
msgid ""
"Provide a meaningful note for your fellow administrators to remind yourself "
"why you've chosen to block the number."
msgstr ""

#: ../system/integrations/cti/includes/outbound-calls.include.rst:18
#: ../system/integrations/cti/includes/outbound-calls.include.rst:17
#: ../system/integrations/cti/sipgate.rst:40
msgid "Outbound"
msgstr ""

#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1
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:11
msgid "Destination caller ID"
msgstr ""

#: ../system/integrations/cti/includes/outbound-calls.include.rst:5
msgid "The caller ID or number you're trying to call."
msgstr ""

#: ../system/integrations/cti/includes/outbound-calls.include.rst:7
msgid "You can use wildcards for e.g. country specific outbound numbers like:"
msgstr ""

#: ../system/integrations/cti/includes/outbound-calls.include.rst:9
msgid "``49*`` for Germany"
msgstr ""

#: ../system/integrations/cti/includes/outbound-calls.include.rst:10
msgid "``4930*`` for Berlin / Germany landlines"
msgstr ""

#: ../system/integrations/cti/includes/outbound-calls.include.rst:11
msgid "``33*`` for France"
msgstr ""

#: ../system/integrations/cti/includes/outbound-calls.include.rst:15
msgid "Set Outbound caller ID"
msgstr ""

#: ../system/integrations/cti/includes/outbound-calls.include.rst:14
msgid ""
"The 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:18
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 :docs:`CTI API </cti/api-intro.html>` in case "
"you're not sure."
msgstr ""

#: ../system/integrations/cti/generic.rst:52
#: ../system/integrations/cti/placetel.rst:54
#: ../system/integrations/cti/sipgate.rst:59
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:73
msgid "Caller Log Filter"
msgstr ""

#: ../system/integrations/cti/generic.rst:55
msgid ""
"This function allows you to provide call information based on e.g. queues "
"only to agents that really need the information."
msgstr ""

#: ../system/integrations/cti/generic.rst:58
msgid ""
"Why? If you have a team for several countries or departments, you don't want "
"to bug your agents from other departments. Leaving these options empty will "
"fallback to showing everything to everyone."
msgstr ""

#: ../system/integrations/cti/generic.rst:64
msgid "Destination caller ID or Queue"
msgstr ""

#: ../system/integrations/cti/generic.rst:63
msgid ""
"This depends on your PBX and usually is either a queue ID, phone number or "
"extension."
msgstr ""

#: ../system/integrations/cti/generic.rst:69
msgid "Agents"
msgstr ""

#: ../system/integrations/cti/generic.rst:67
msgid ""
"Select the agents that are responsible for the group. These agents will then "
"see caller log entries and call notifications fitting to said queue."
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/recent-logs.include.rst:31
msgid "x"
msgstr ""

#: ../system/integrations/cti/includes/troubleshooting.include.rst:10
#: ../system/integrations/cti/includes/troubleshooting.include.rst:9
msgid "My Phone page stays blank, signalling does work..."
msgstr ""

#: ../system/integrations/cti/includes/troubleshooting.include.rst:5
msgid ""
"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 dialog 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:8
msgid ""
"To see it work from the agent's perspective, have a look on :user-docs:`user "
"documentation </extras/caller-log.html>`."
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:32
msgid ""
"The here listed endpoint settings are relevant for the :doc:`integration "
"configuration with Placetel <provider-configurations/placetel>`."
msgstr ""

#: ../system/integrations/cti/placetel.rst:37
#: ../system/integrations/i-doit.rst:53
msgid "Endpoint"
msgstr ""

#: ../system/integrations/cti/placetel.rst:36
msgid ""
"This endpoint will be required for the Zammad integration within the "
"Placetel web interface."
msgstr ""

#: ../system/integrations/cti/placetel.rst:41
msgid "API Token"
msgstr ""

#: ../system/integrations/cti/placetel.rst:40
msgid ""
"You'll receive this token within the ``Web API`` menu. Make sure to copy "
"this value, it's only shown once!"
msgstr ""

#: ../system/integrations/cti/placetel.rst:71
#: ../system/integrations/cti/sipgate.rst:77
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:64
msgid ""
"You can find your agents Placetel username combination required within ⚙️ PBX "
"→ VoIP destinations. Within the \"Advanced settings\" section you're looking "
"for \"SIP user name\" and \"SIP server\"."
msgstr ""

#: ../system/integrations/cti/placetel.rst:68
msgid "Combine these two like so: ``<sip-user-name>@<sip-server>``."
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 "
"<https://web.placetel.de>`_."
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:29
msgid "Step 1: Activate Zammad integration"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:14
msgid ""
"Within Integrations, scroll down to Partner integrations and select Zammad."
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:17
msgid ""
"You can alternatively filter by \"Ticket Systems\" to reduce the number of "
"entries on the page. You'll still want to look for Partner integrations. 🤓"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:21
msgid ""
"Within the Zammad integration now press \"Activate\". A new tab ``API`` "
"becomes available - open this tab."
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:24
msgid ""
"Now tick \"Enable Call Control / Notify API\" and paste the Placetel "
"endpoint from your Zammad instance into the field \"URL of your API "
"endpoint\". Save to apply the settings"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:0
msgid "Screencast showing how to activate the Zammad integration"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:51
msgid "Step 2: Generate API Token for Placetel"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:32
msgid ""
"Go back to the integrations page and scroll down to \"Web API\". Generate a "
"new API token by using the \"Create a new API token\" button."
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:37
msgid ""
"If you already generated a token either use your existing token or reset it "
"by using above mentioned button. Placetel will ask you to conform this reset."
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:41
msgid ""
"Please keep in mind that existing API scripts may no longer work due to "
"token resets!"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:44
msgid ""
"Copy the provided API token and insert it into the \"API Token\" field "
"within Zammad's Placetel integration."
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:47
msgid ""
"Apply your changes by using the \"Save\" button on the bottom of the "
"Placetel integration page and activate the Placetel integration."
msgstr ""

#: ../system/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:73
#: ../system/integrations/cti/provider-configurations/sipgate.rst:77
msgid "Step 3: Restrict the numbers to notify on"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:54
msgid ""
"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:58
msgid ""
"Lower on the page Placetel allows you to restrict the numbers to notify on. "
"You'll find this within the \"External routing API\" part."
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:0
msgid ""
"Screenshot showing a sample selection of phone numbers to use for the "
"Placetels notify API"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:66
msgid ""
"This menu point also provides a API request log from Placetel view. Just "
"open \"Recent responses of your API endpoint\" to learn more."
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:69
msgid ""
"If you want to see Zammad's perspective, use the \"Recent Logs\" part from "
"within the Placetel integration page."
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:0
msgid "Screenshot showing sample log entries for Placetels API calls to Zammad"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:77
msgid "Step 4 (optional): Further configurations for Placetel"
msgstr ""

#: ../system/integrations/cti/provider-configurations/placetel.rst:76
msgid ""
"If needed, you can now configure Zammad's Placetel integration in more "
"detail. You can learn more about your options here: :ref:`Placetel "
"integration settings <placetel_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 <https://www.sipgate.io/pricing>`_ before!"
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:35
msgid "Step 1: Book sipgate.io package"
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:13
msgid "Skip to step 2 if you already have the package booked!"
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:15
msgid ""
"Login to an administrative Sipgate account and navigate to "
"``Accountverwaltung``. You'll see several different options depending on "
"your booked packages. Select ``Verträge & Produkte`` to continue."
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:19
msgid ""
"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for "
"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-"
"Button."
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:23
msgid ""
"On the next page select either one of the ``sipgate.io`` packages or ``Push-"
"API Package Free``. Follow the dialogue by booking the addon. You'll be "
"returned to your contract overview and now should see the selected addon in "
"your list."
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:30
msgid ""
"The availability for ``sipgate.io`` packages and their levels highly depends "
"on the overall account type and product you've booked with Sipgate."
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:52
msgid "Step 2: Configure webhook for Zammad"
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:38
msgid ""
"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. "
"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste "
"the endpoint URLs from your Zammad instance like so:"
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:42
msgid "Inbound endpoint to \"Incoming\""
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:43
msgid "Outbound endpoint to \"Outgoing\""
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:47
msgid ""
"Ensure to select at least one call group or phoneline within \"Sources\". "
"Other wise Sipgate will not indicate any incoming or outgoing calls to "
"Zammad."
msgstr ""

#: ../system/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:55
msgid ""
"Having a lot of numbers that shouldn't be used for notifying Zammad? Within "
"the Webhooks → URLs section of Sipgate you can select which *sources* "
"Sipgate should notify Zammad about in- and outgoing calls."
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:59
msgid ""
"Use either specific phone lines or use the option \"Use for all phonelines "
"and groups\" to notify Zammad about all existing lines of your Sipgate "
"account."
msgstr ""

#: ../system/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:68
msgid "This section also allows you to enable a Debug log."
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:0
msgid "Screenshot showing an enabled Debug log option"
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:73
msgid ""
"After enabling you can use the Debug log section to see all sent webhook "
"calls to Zammad. You'll also can see the response."
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:81
msgid "Step 4 (optional): Further configurations for Sipgate"
msgstr ""

#: ../system/integrations/cti/provider-configurations/sipgate.rst:80
msgid ""
"If needed, you can now configure Zammad's Sipgate integration in more "
"detail. You can learn more about your options here: :ref:`Sipgate "
"integration settings <sipgate_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:17
msgid ""
"Zammad requires a ``sipgate.io`` addon from the feature store (please note "
"that API calls are not free with Sipgate. Rates may apply and differ from "
"account to account)."
msgstr ""

#: ../system/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:33
msgid ""
"Below endpoint settings affect the :doc:`sipgate.io configuration <provider-"
"configurations/sipgate>`."
msgstr ""

#: ../system/integrations/cti/sipgate.rst:37
msgid "This endpoint is required for incoming call hooks."
msgstr ""

#: ../system/integrations/cti/sipgate.rst:40
msgid "This endpoint is required for outgoing call hooks."
msgstr ""

#: ../system/integrations/cti/sipgate.rst:0
msgid "Screenshot showing sample user mappings in between Sipgate and Zammad"
msgstr ""

#: ../system/integrations/cti/sipgate.rst:69
msgid ""
"You can find your agent's Sipgate username within ``Accountverwaltung → "
"Benutzer``. You're looking for the SIP-ID."
msgstr ""

#: ../system/integrations/cti/sipgate.rst:0
msgid "Sample VoIP credentials for a Sipgate user"
msgstr ""

#: ../system/integrations/cti/sipgate.rst:77
msgid "Users with several devices also have several SIP-IDs."
msgstr ""

#: ../system/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 :docs:`Grafana </appendix/reporting-tools-thirdparty/grafana.html>` "
"setup page as well."
msgstr ""

#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.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:72
msgid ""
"If you require all indexes or our listing is not good enough for you, point "
"your browser to the URL we're providing and append ``/_aliases?"
"pretty=true``. The result should look like this: ``https://<URL>.zammad.com/"
"_aliases?pretty=true``."
msgstr ""

#: ../system/integrations/elasticsearch.rst:77
msgid ""
"Your browser will automatically ask for your credentials - you'll then see "
"something like this:"
msgstr ""

#: ../system/integrations/elasticsearch.rst:125
msgid "Credentials"
msgstr ""

#: ../system/integrations/elasticsearch.rst:127
msgid ""
"Within this section Zammad displays your available users. The password is "
"provided once (upon activation) and cannot be retrieved after that."
msgstr ""

#: ../system/integrations/elasticsearch.rst:131
msgid ""
"If you need to change or reset your Elasticsearch user password, use the "
"\"Reset password\" button in the credentials table. Doing so creates a brand "
"new password for the account in question. This change is immediate, keep in "
"mind that this may affect third party tools connected to your instance."
msgstr ""

#: ../system/integrations/exchange.rst:2
msgid "Exchange"
msgstr ""

#: ../system/integrations/exchange.rst:4
msgid ""
"With Zammad's Exchange integration, you can easily use existing address "
"books without having to update more than one source."
msgstr ""

#: ../system/integrations/exchange.rst:7
msgid ""
"However, you should refrain from syncing all addresses, as the results may "
"not be what you expect (Exchange collects huge amounts of addresses). A "
"central address book of your company to sync makes more sense, as you can "
"ensure that Zammad gets only the data you need and want. Apart from this, it "
"is even not possible to sync the Global Address List (GAL) of your Exchange "
"system with Zammad."
msgstr ""

#: ../system/integrations/exchange.rst:16
msgid ""
"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP "
"integration. If you have the same users in both sources, the LDAP version "
"will always be Zammad's pick."
msgstr ""

#: ../system/integrations/exchange.rst:19
msgid ""
"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes "
"to your users inside of Zammad might be overwritten by the Exchange sync."
msgstr ""

#: ../system/integrations/exchange.rst:24
msgid ""
"To configure Exchange integration, simply go to the System > Integrations > "
"Exchange in the admin panel. Press \"change\" and follow the wizard for "
"adding the needed Exchange information to Zammad. On the last two steps "
"Zammad will ask you for the address book(s) and your desired attribute "
"mapping. By default, Zammad only maps email address, first- and lastname. "
"Technically, you can map any Exchange object to a Zammad user object (this "
"also works for custom objects!)."
msgstr ""

#: ../system/integrations/exchange.rst:35
msgid ""
"If the SSL verification fails while connecting to Exchange, Zammad will ask "
"you to turn it off temporarily."
msgstr ""

#: ../system/integrations/exchange.rst:38
msgid ""
"Please be aware that **turning off SSL verification is a security risk**. It "
"should only be used temporarily or for testing purposes. If turned off, "
"there is no verification of the certificate, which means that every "
"presented certificate will be accepted."
msgstr ""

#: ../system/integrations/exchange.rst:43
msgid ""
"After pressing Continue, Zammad will check if the configuration is okay. You "
"can then enable Exchange and start your first sync. The sync will then run "
"hourly - if you need to change mappings or the address book(s), you can "
"change the configuration at any time."
msgstr ""

#: ../system/integrations/exchange.rst:50
msgid ""
"After the sync has finished, you can find the new Exchange contacts under "
"\"Users\". Zammad integrates them just as normal users."
msgstr ""

#: ../system/integrations/exchange.rst:55
msgid ""
"In some cases you might see unique IDs as \"Login\" instead of the email "
"address. This is normal and doesn't affect the login or email mapping for "
"that entry."
msgstr ""

#: ../system/integrations/github.rst:4
msgid ""
"Use GitHub integration to track GitHub issues directly within Zammad "
"tickets. Add issue hyperlinks and get a live summary of metadata like status "
"(open/closed), assignee, labels, and more."
msgstr ""

#: ../system/integrations/github.rst:8
msgid "Please note that our GitHub integration does not support pull requests."
msgstr ""

#: ../system/integrations/github.rst:None
msgid "Integration page for GitHub"
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 <https://docs.github.com/en/developers/apps/scopes-for-"
"oauth-apps>`_, which presents a security risk if your token ever falls into "
"the wrong hands."
msgstr ""

#: ../system/integrations/github.rst:37
msgid ""
"Unfortunately, because of how GitHub's OAuth token scopes are set up, this "
"is the only way to link issues on private repos."
msgstr ""

#: ../system/integrations/github.rst:40
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:47
msgid ""
"Use the default API endpoint (``https://api.github.com/graphql``) unless "
"you're using GitHub Enterprise Server."
msgstr ""

#: ../system/integrations/github.rst:50
msgid ""
"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉"
msgstr ""

#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52
msgid "Token verification is taking a long time"
msgstr ""

#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49
msgid ""
"Slight delays are normal (<2 min.), especially for systems under heavy load."
msgstr ""

#: ../system/integrations/github.rst:58
msgid ""
"Self-hosted administrators, please check your network settings to ensure "
"that your Zammad server can reach ``api.github.com``."
msgstr ""

#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55
msgid "I reloaded the page and now the API token is gone"
msgstr ""

#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55
msgid ""
"This may indicate that Zammad is still verifying your API token. Try "
"reloading the page again in a couple minutes."
msgstr ""

#: ../system/integrations/gitlab.rst:2
msgid "GitLab"
msgstr ""

#: ../system/integrations/gitlab.rst:4
msgid ""
"Use GitLab integration to track GitLab issues directly within Zammad "
"tickets. Add issue hyperlinks and get a live summary of metadata like status "
"(open/closed), assignee, labels, and more."
msgstr ""

#: ../system/integrations/gitlab.rst:8
msgid ""
"Please note that our GitLab integration does not support merge requests."
msgstr ""

#: ../system/integrations/gitlab.rst:None
msgid "Integration page for GitLab"
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 ""
"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless "
"you're a self-hosted GitLab user."
msgstr ""

#: ../system/integrations/gitlab.rst:43
msgid ""
"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉"
msgstr ""

#: ../system/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 <https://www.i-doit.com/>`_ 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:10
msgid ""
"What's that got to do with Zammad? Well, if you used tickets to track issues "
"with all that hardware, you might start wishing there was a way they could "
"talk to each other."
msgstr ""

#: ../system/integrations/i-doit.rst:14
msgid "Zammad gives you two:"
msgstr ""

#: ../system/integrations/i-doit.rst:17
msgid "1. Add i-doit Links to Zammad Tickets"
msgstr ""

#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80
msgid "What Users See"
msgstr ""

#: ../system/integrations/i-doit.rst:26
msgid "i-doit integration in Zammad's ticket pane"
msgstr ""

#: ../system/integrations/i-doit.rst:26
msgid ""
"The i-doit integration will appear under a new 🖨 tab in the ticket pane."
msgstr ""

#: ../system/integrations/i-doit.rst:28
msgid ""
"i-doit integration puts a new tab in Zammad's ticket pane where you can add "
"links to existing i-doit devices for easy reference. (See our :user-docs:"
"`user documentation </extras/i-doit-track-company-property.html>` to learn "
"how it works in practice)."
msgstr ""

#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93
msgid "How to Set it Up"
msgstr ""

#: ../system/integrations/i-doit.rst:38
msgid ""
"It requires i-doit's `API Add-on <https://www.i-doit.com/i-doit/add-ons/api-"
"add-on/>`_. Make sure to have it properly set up. Use the following setting:"
msgstr ""

#: ../system/integrations/i-doit.rst:42
msgid "Active: ``Yes``"
msgstr ""

#: ../system/integrations/i-doit.rst:43
msgid "Enforce authentication by username and password: ``No``"
msgstr ""

#: ../system/integrations/i-doit.rst:45
msgid ""
"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:53
msgid "The root URL of your i-doit installation."
msgstr ""

#: ../system/integrations/i-doit.rst:62
msgid "API token"
msgstr ""

#: ../system/integrations/i-doit.rst:56
msgid ""
"Found in the i-doit admin panel under **Interfaces / external data > JSON-"
"RPC API > Common Settings**."
msgstr ""

#: ../system/integrations/i-doit.rst:0
msgid "i-doit administration interface with API configuration"
msgstr ""

#: ../system/integrations/i-doit.rst:67
msgid "Client ID"
msgstr ""

#: ../system/integrations/i-doit.rst:65
msgid "A unique name to identify Zammad within i-doit."
msgstr ""

#: ../system/integrations/i-doit.rst:67
msgid "(Zammad does not require you to enter a value here, but i-doit might!)"
msgstr ""

#: ../system/integrations/i-doit.rst:70
msgid ""
"Here you can decide if the certificate of your i-doit system has to be "
"verified or not. In case you are using custom certificates, please have a "
"look at :doc:`how to add them to Zammad </settings/security/ssl-"
"certificates>`."
msgstr ""

#: ../system/integrations/i-doit.rst:77
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:86
msgid ""
"i-doit's ticket system integration gives you a way to see all the tickets "
"for a given device without ever leaving i-doit. (See our :user-docs:`user "
"documentation </extras/i-doit-track-company-property.html>` to learn how it "
"works in practice)."
msgstr ""

#: ../system/integrations/i-doit.rst:95
msgid ""
"Enable this integration in the i-doit admin panel under **Interfaces / "
"external data > Trouble Ticket System (TTS) > Configuration**:"
msgstr ""

#: ../system/integrations/i-doit.rst:None
msgid "i-doit administration interface with TTS configuration"
msgstr ""

#: ../system/integrations/i-doit.rst:104
msgid "TTS-Type"
msgstr ""

#: ../system/integrations/i-doit.rst:104
msgid "``Zammad``"
msgstr ""

#: ../system/integrations/i-doit.rst:115
msgid "Username / Password"
msgstr ""

#: ../system/integrations/i-doit.rst:107
msgid "Login credentials for a Zammad agent."
msgstr ""

#: ../system/integrations/i-doit.rst:109
msgid ""
"This agent must have **read permission** for all :doc:`groups </manage/"
"groups/index>` that plan on using the i-doit integration."
msgstr ""

#: ../system/integrations/i-doit.rst:113
msgid ""
"You may even wish to create a dedicated agent account just for this "
"integration (otherwise, if the agent ever changes her password, you will "
"have to remember to update it here)."
msgstr ""

#: ../system/integrations/i-doit.rst:117
msgid "URL incl. protocol"
msgstr ""

#: ../system/integrations/i-doit.rst:118
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 <https://community.zammad.org/c/stuff-you-like-zammad-"
"to-have-feel-free-to-discuss-and-add-proposals/6>`_."
msgstr ""

#: ../system/integrations/index.rst:31
msgid "Integrations for Authentication and Customers"
msgstr ""

#: ../system/integrations/index.rst:44
msgid "Integrations for Monitoring Systems"
msgstr ""

#: ../system/integrations/index.rst:46
msgid "This section currently misses the following integrations:"
msgstr ""

#: ../system/integrations/index.rst:48
msgid "Icinga"
msgstr ""

#: ../system/integrations/index.rst:49
msgid "Monit"
msgstr ""

#: ../system/integrations/index.rst:50
msgid "Nagios"
msgstr ""

#: ../system/integrations/index.rst:60
msgid "Integrations for Issue Trackers"
msgstr ""

#: ../system/integrations/index.rst:70
msgid "Other Integrations"
msgstr ""

#: ../system/integrations/index.rst:72
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 :docs:`Kerberos "
"Single Sign-On </appendix/single-sign-on.html>` 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:25
msgid "📝 :doc:`manage`"
msgstr ""

#: ../system/integrations/ldap/index.rst:25
msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed."
msgstr ""

#: ../system/integrations/ldap/index.rst:30
msgid "Before you continue, please note the following limitations."
msgstr ""

#: ../system/integrations/ldap/index.rst:32
msgid "Mapping / Synchronizing organizations is not possible"
msgstr ""

#: ../system/integrations/ldap/index.rst:36
msgid ""
"You may want to consider using domain based assignments to overcome this "
"issue. Learn more on :doc:`/manage/organizations/index`."
msgstr ""

#: ../system/integrations/ldap/index.rst:39
msgid ""
"Zammad's LDAP sync is one way. Editing user settings or permissions may be "
"overwritten upon the next sync depending on your configuration."
msgstr ""

#: ../system/integrations/ldap/index.rst:41
msgid "Nested groups are not supported."
msgstr ""

#: ../system/integrations/ldap/index.rst:42
msgid "Synchronizing user avatars from LDAP is not supported."
msgstr ""

#: ../system/integrations/ldap/index.rst:43
msgid "Unlike user filters, group filters cannot be changed."
msgstr ""

#: ../system/integrations/ldap/index.rst:44
msgid ""
"When a user originates from an LDAP server, Zammad will try to verify the "
"login credentials against LDAP first - if this fails Zammad will check its "
"local database."
msgstr ""

#: ../system/integrations/ldap/index.rst:50
msgid ""
"Users can have local passwords even if they're LDAP users! You can learn "
"more about user accounts in general on :doc:`/manage/users/index`."
msgstr ""

#: ../system/integrations/ldap/index.rst:54
msgid ""
"When several LDAP sources contain the same user (meaning the same email "
"address), the user in question will be updated with every source configured. "
"*The last LDAP source will win.*"
msgstr ""

#: ../system/integrations/ldap/index.rst:58
msgid ""
"This is subject to change with `Issue 4109 <https://github.com/zammad/zammad/"
"issues/4109>`_ in the future."
msgstr ""

#: ../system/integrations/ldap/index.rst:60
msgid ""
"Synchronization statistics currently affect *all* configured LDAP sources. "
"This also applies for newly added or updated sources."
msgstr ""

#: ../system/integrations/ldap/index.rst:63
msgid ""
"This is subject to change with `Issue 4108 <https://github.com/zammad/zammad/"
"issues/4108>`_ in the future."
msgstr ""

#: ../system/integrations/ldap/index.rst:65
msgid ""
"Zammad currently has limited fallback server support. You can workaround "
"this by providing several sources - however, ensure to have the exact same "
"configuration on your fallback."
msgstr ""

#: ../system/integrations/ldap/index.rst:69
msgid ""
"This is subject to improve with `Issue 4107 <https://github.com/zammad/"
"zammad/issues/4107>`_ in the future."
msgstr ""

#: ../system/integrations/ldap/index.rst:76
msgid ""
"This section holds all requests Zammad handled for all LDAP sources. These "
"entries can either contain synchronization information or logins "
"(authentication attempts via Zammad's login interface)."
msgstr ""

#: ../system/integrations/ldap/index.rst:80
msgid ""
"By clicking on any request, Zammad will provide even more information. The "
"provided information can be useful when something does not work as expected."
msgstr ""

#: ../system/integrations/ldap/index.rst:85
msgid ""
"Especially a LDAP synchronization can cause many log entries. The web "
"interface will always limit the number of shown entries to the last 50 "
"entries."
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:65
msgid "Add new source"
msgstr ""

#: ../system/integrations/ldap/manage.rst:10
msgid ""
"Using the *New Source* button allows you to add new LDAP sources to your "
"installation. You're not limited in the number of sources, however, keep in "
"mind that many sources will also take more time to synchronize."
msgstr ""

#: ../system/integrations/ldap/manage.rst:14
msgid ""
"You can choose between different encryption types, namely *SSL* and "
"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or "
"*STARTTLS*, Zammad will display an additional *SSL verification* option that "
"allows you to disable the verification, e.g. for self-signed SSL "
"certificates. You can also tell Zammad to use a different port by appending "
"``:<port number>`` to your hostname/IP."
msgstr ""

#: ../system/integrations/ldap/manage.rst:0
msgid ""
"Screenshot of configuring a new LDAP source with SSL encryption and SSL "
"verification"
msgstr ""

#: ../system/integrations/ldap/manage.rst:26
msgid ""
"New Source with SSL transport security enabled and certificate verification"
msgstr ""

#: ../system/integrations/ldap/manage.rst:30
msgid ""
"Using an user filter can be a good idea if you only require a small subset "
"of your LDAP users in Zammad."
msgstr ""

#: ../system/integrations/ldap/manage.rst:42
msgid "This especially affects inactive users"
msgstr ""

#: ../system/integrations/ldap/manage.rst:34
msgid ""
"As every LDAP behaves differently on which attributes and how they are set, "
"Zammad doesn't care about any flags."
msgstr ""

#: ../system/integrations/ldap/manage.rst:37
msgid ""
"Users that no longer are returned by your LDAP source will automatically be "
"set to inactive. Zammad assumes that the user was deactivated."
msgstr ""

#: ../system/integrations/ldap/manage.rst:41
msgid ""
"Users will never be removed automatically! If you want to remove obsolete "
"users, use :doc:`/system/data-privacy`."
msgstr ""

#: ../system/integrations/ldap/manage.rst:46
msgid "Active Directory admins"
msgstr ""

#: ../system/integrations/ldap/manage.rst:45
msgid ""
"Active Directories are quite specific on how to filter for active users only "
"- please see the `Microsoft documentation <https://blogs.msdn.microsoft.com/"
"muaddib/2008/10/08/how-to-query-individual-properties-of-the-"
"useraccountcontrol-active-directory-user-property-using-ldap/>`_ for more "
"information."
msgstr ""

#: ../system/integrations/ldap/manage.rst:51
msgid ""
"*Do not* manually write pathes of either LDAP attributes or groups. If "
"Zammad does not display them, it either cannot find them or you have a lot "
"of users that don't have the attributes populated."
msgstr ""

#: ../system/integrations/ldap/manage.rst:55
msgid ""
"Zammad will always only return attributes that are filled - this reduces the "
"returned list of attributes greatly."
msgstr ""

#: ../system/integrations/ldap/manage.rst:0
msgid "Screencast showing how to add a new LDAP source"
msgstr ""

#: ../system/integrations/ldap/manage.rst:63
msgid ""
"If your LDAP system doesn't allow anonymous bind, Zammad detects it and "
"provides you an editable \"Base DN\" *text* field instead of a prefilled "
"*select* field."
msgstr ""

#: ../system/integrations/ldap/manage.rst:81
msgid "Review or edit existing source"
msgstr ""

#: ../system/integrations/ldap/manage.rst:68
msgid ""
"Clicking on a LDAP source will provide a configuration and mapping overview."
msgstr ""

#: ../system/integrations/ldap/manage.rst:70
msgid ""
"If needed you can then use the *Change* button to update either the name, "
"active state or the whole configuration. If you're changing the whole "
"configuration, the dialogue will be identical to the source creation."
msgstr ""

#: ../system/integrations/ldap/manage.rst:76
msgid ""
"Did your LDAP server change? Different LDAP servers have different "
"structures and default attributes. This causes the LDAP synchronization to "
"likely fail. Consider removing the affected source and re-add it."
msgstr ""

#: ../system/integrations/ldap/manage.rst:0
msgid "Screencast showing the update of the source name."
msgstr ""

#: ../system/integrations/ldap/manage.rst:89
msgid "Re-arrange LDAP source's order"
msgstr ""

#: ../system/integrations/ldap/manage.rst:84
msgid ""
"You can change the synchronization order for each source at any time. Zammad "
"will synchronize the sources from top to bottom."
msgstr ""

#: ../system/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:101
msgid "Remove a source"
msgstr ""

#: ../system/integrations/ldap/manage.rst:92
msgid ""
"If you no longer need the a LDAP source or simply want to start over, you "
"can remove them at any time. This will not remove synchronized users, data "
"synchronized or permissions."
msgstr ""

#: ../system/integrations/ldap/manage.rst:98
msgid ""
"Not sure if you'd need the source later on? Set the source to inactive "
"instead of removing it - see *Review or edit existing source* for more."
msgstr ""

#: ../system/integrations/ldap/manage.rst:0
msgid "Screencast showing how to remove LDAP sources."
msgstr ""

#: ../system/integrations/pgp/index.rst:2
msgid "PGP"
msgstr ""

#: ../system/integrations/pgp/index.rst:7
msgid ""
"Pretty Good Privacy (PGP) is another method for secure email communication. "
"With PGP, you can exchange **signed** and **encrypted** messages with others."
msgstr ""

#: ../system/integrations/pgp/index.rst:13
#: ../system/integrations/smime/index.rst:17
msgid "Signing"
msgstr ""

#: ../system/integrations/pgp/index.rst:11
msgid "is a proof that a message hasn't been manipulated on its way."
msgstr ""

#: ../system/integrations/pgp/index.rst:13
msgid ""
"In other words, it guarantees message **integrity** and **authenticity**."
msgstr ""

#: ../system/integrations/pgp/index.rst:19
#: ../system/integrations/smime/index.rst:22
msgid "Encryption"
msgstr ""

#: ../system/integrations/pgp/index.rst:16
#: ../system/integrations/smime/index.rst:20
msgid ""
"scrambles a message so that it can only be unscrambled by the intended "
"recipient."
msgstr ""

#: ../system/integrations/pgp/index.rst:19
msgid ""
"In other words, it guarantees message **privacy** and **data security**."
msgstr ""

#: ../system/integrations/pgp/index.rst:25
msgid "Screenshot of ticket creation with encrypt and sign buttons"
msgstr ""

#: ../system/integrations/pgp/index.rst:25
msgid ""
"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will "
"appear in the ticket composer."
msgstr ""

#: ../system/integrations/pgp/index.rst:28
msgid "**Sign button not visible?**"
msgstr ""

#: ../system/integrations/pgp/index.rst:30
msgid ""
"Please note that the signing of emails is based on the outgoing email "
"account. That means you have to choose a group with a sender email account, "
"which has a private key assigned."
msgstr ""

#: ../system/integrations/pgp/index.rst:35
msgid "Handling of Keys"
msgstr ""

#: ../system/integrations/pgp/index.rst:36
msgid ""
"To use the PGP function, you have to enable the integration (PGP) by "
"switching the toggle to *enabled*."
msgstr ""

#: ../system/integrations/pgp/index.rst:39
msgid ""
"You can add keys by clicking the *add key* button. The keys can be imported "
"from a file or you can paste the content of the key in the text box."
msgstr ""

#: ../system/integrations/pgp/index.rst:42
msgid "**Which keys do I have to import?**"
msgstr ""

#: ../system/integrations/pgp/index.rst:44
msgid ""
"For **signing** *outgoing* emails, you have to import the private key of "
"your Zammad email account."
msgstr ""

#: ../system/integrations/pgp/index.rst:47
msgid ""
"For **encrypting** *outgoing* emails, you have to import the public key of "
"the customer's email account."
msgstr ""

#: ../system/integrations/pgp/index.rst:50
msgid ""
"For **verifying the signature** of signed *incoming* emails, you have to "
"import the public key of the customer."
msgstr ""

#: ../system/integrations/pgp/index.rst:53
msgid ""
"For **decrypting** of encrypted *incoming* emails, you have to import the "
"private key of your Zammad email account."
msgstr ""

#: ../system/integrations/pgp/index.rst:57
msgid "Import Keys From a File"
msgstr ""

#: ../system/integrations/pgp/index.rst:58
msgid "You can import keys from a file in the section **Upload key**:"
msgstr ""

#: ../system/integrations/pgp/index.rst:None
msgid "Screenshot of adding a key via file"
msgstr ""

#: ../system/integrations/pgp/index.rst:64
msgid ""
"**Supported file formats:** ASCII-armor as well as binary GPG format "
"(basically any GPG supported key format) is supported here."
msgstr ""

#: ../system/integrations/pgp/index.rst:68
msgid "Import Keys by Pasting the Content"
msgstr ""

#: ../system/integrations/pgp/index.rst:69
msgid "You can also paste the key's content in the section **paste key**:"
msgstr ""

#: ../system/integrations/pgp/index.rst:None
msgid "Screenshot of adding a key via pasting"
msgstr ""

#: ../system/integrations/pgp/index.rst:75
msgid ""
"**Supported format:** Please note that only ASCII-armor is supported here."
msgstr ""

#: ../system/integrations/pgp/index.rst:78
msgid "Deleting Keys"
msgstr ""

#: ../system/integrations/pgp/index.rst:79
msgid ""
"If you want to delete a specific key, you can do it by clicking on the menu "
"in the *actions* column and select **delete**:"
msgstr ""

#: ../system/integrations/pgp/index.rst:None
msgid "Screenshot of deleting a key"
msgstr ""

#: ../system/integrations/pgp/index.rst:88
msgid "Downloading Keys"
msgstr ""

#: ../system/integrations/pgp/index.rst:89
msgid ""
"If you want to download your keys, you can do this as well via corresponding "
"action buttons. Depending on the key, you can choose wether you want to "
"download the private or the public key."
msgstr ""

#: ../system/integrations/pgp/index.rst:95
#: ../system/integrations/smime/manage-certificates.rst:76
msgid "Default Behavior"
msgstr ""

#: ../system/integrations/pgp/index.rst:96
msgid ""
"Here you can adjust on per group basis, if *sign* and *encryption* is on or "
"off by default. Please be aware, that agents can always override the setting "
"for each individual article."
msgstr ""

#: ../system/integrations/pgp/index.rst:None
msgid "Adjusting default behavior on per group basis"
msgstr ""

#: ../system/integrations/pgp/index.rst:107
msgid ""
"Here you can see the last actions regarding signing and encryption and if "
"they were successful."
msgstr ""

#: ../system/integrations/pgp/index.rst:117
msgid "**Sign button is not visible, but keys are imported.**"
msgstr ""

#: ../system/integrations/pgp/index.rst:115
msgid "Did you choose a group in the ticket?"
msgstr ""

#: ../system/integrations/pgp/index.rst:116
msgid ""
"Did you import a private key for the email adress, which is used for "
"outgoing emails in the group?"
msgstr ""

#: ../system/integrations/pgp/index.rst:122
msgid "**How to obtain keys?**"
msgstr ""

#: ../system/integrations/pgp/index.rst:120
msgid ""
"You can create them yourself! There are some good tutorials on the web on "
"how to create them. Providing keys to Zammad is a prerequisite to use the "
"PGP feature."
msgstr ""

#: ../system/integrations/pgp/index.rst:127
msgid "**It says a passphrase is needed, but I haven't got one.**"
msgstr ""

#: ../system/integrations/pgp/index.rst:125
msgid ""
"If the key is secured with a passphrase, you have to provide it for the "
"import in Zammad. It is possible that keys may have an empty passphrase. "
"However, this is *not* recommended."
msgstr ""

#: ../system/integrations/pgp/index.rst:132
msgid "**How do my customers get my new key?**"
msgstr ""

#: ../system/integrations/pgp/index.rst:130
msgid ""
"You have to provide your **public** key in advance. Your customer also has "
"to configure PGP in their email workflow and import your public key. The "
"other way round, you have to get the public key of your customer and have to "
"import it to Zammad."
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 :doc:`pre-defined webhooks </manage/webhook/"
"examples/slack-notifications>` instead. Existing Slack integrations should "
"be migrated manually before this feature is dropped."
msgstr ""

#: ../system/integrations/slack.rst:14
msgid ""
"In order to use this feature, please add a new Slack app to your Workspace. "
"The App you need is called ``Incoming WebHooks`` ."
msgstr ""

#: ../system/integrations/slack.rst:18
msgid "Why Do I Need This Feature?"
msgstr ""

#: ../system/integrations/slack.rst:20
msgid ""
"If you're already using Slack for your team communication, you'll love this "
"feature! Our Slack integration can push ticket notifications about the last "
"ticket article based on the following events:"
msgstr ""

#: ../system/integrations/slack.rst:24
msgid "on Ticket creation"
msgstr ""

#: ../system/integrations/slack.rst:25
msgid "on Ticket updates"
msgstr ""

#: ../system/integrations/slack.rst:26
msgid "on reached reminders"
msgstr ""

#: ../system/integrations/slack.rst:27
msgid "a Ticket has escalated"
msgstr ""

#: ../system/integrations/slack.rst:28
msgid "a Ticket is going to escalate"
msgstr ""

#: ../system/integrations/slack.rst:30
msgid ""
"Zammad will provide the Ticket title, a direct link to the Ticket, the event "
"type (creation, updated, escalation), the customer, time and the last "
"article that has triggered the notification."
msgstr ""

#: ../system/integrations/slack.rst:34
msgid ""
"This will give you further options, as you can see e.g. escalating tickets "
"that are assigned to an agent that's e.g. absent. You can interact faster, "
"as you might see problems earlier (or even before the problem gets one)."
msgstr ""

#: ../system/integrations/slack.rst:38
msgid ""
"If needed and wanted, you can even discuss directly about the topic before "
"sending an answer to the customer. Another possible use case would be a "
"agent monitoring new agents and their answers to tickets."
msgstr ""

#: ../system/integrations/slack.rst:44
msgid "Configure the Integration"
msgstr ""

#: ../system/integrations/slack.rst:46
msgid ""
"First of all, please go to your slack workspace - go to administration => "
"Manage Apps. If you don't have an app yet, you can simply add a new one - "
"just search for ``Incoming WebHooks`` and customize the app to your needs."
msgstr ""

#: ../system/integrations/slack.rst:50
msgid ""
"Choose (or create) the channel Zammad should post it's information to and "
"press on \"Add Incoming WebHooks integration\". If you're ready, copy the "
"provided WebHook URL and go to your Zammad installation."
msgstr ""

#: ../system/integrations/slack.rst:56
msgid ""
"You need administrative rights on the Slack Workspace. The link to the app "
"directory is normally ``https://[workspace-name].slack.com/apps`` ."
msgstr ""

#: ../system/integrations/slack.rst:63
msgid ""
"To configure the slack integration, log in to Zammad and go to Integrations "
"(System) => Slack in the admin panel."
msgstr ""

#: ../system/integrations/slack.rst:66
msgid ""
"Here you can choose on what evens Zammad should post information about a "
"ticket to your Slack channel. Next you need to device what groups shall be "
"affected by this, as anybody with access to that specific Slack channel can "
"read at least parts of the ticket this might be a privacy issue, if you "
"select the wrong groups. The username is simply the name that Zammad uses as "
"display name inside the Slack chat. The channel defines the Slack channel "
"the information is being posted in. As last option, you can set a custom "
"icon for posting to slack."
msgstr ""

#: ../system/integrations/slack.rst:74
msgid ""
"When you're ready, just hit \"Submit\" and enable the integration. Zammad "
"will now post new ticket information based on the trigger you chose. Below "
"the options you have the recent log that shows the latest requests to Slack "
"for debugging if needed."
msgstr ""

#: ../system/integrations/slack.rst:81
msgid ""
"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. "
"The icon should be a square PNG file."
msgstr ""

#: ../system/integrations/slack.rst:90
msgid ""
"The following figure shows how it will look if you choose to receive updates "
"on created and updated tickets. On every post Zammad sends to the Slack "
"channel, you can create new threads to discuss about the new article."
msgstr ""

#: ../system/integrations/slack.rst:96
msgid ""
"If you just want to keep track of soon escalating or already escalated "
"tickets, it will look the the following figure. Zammad changes the color in "
"front of the post so you can easily see the state of the ticket."
msgstr ""

#: ../system/integrations/slack.rst:102
msgid ""
"If you change the state, Zammad will also put information on what state the "
"ticket gets and (if pending state) the date until it pends. You'll also "
"recognize the color codes in front of posts on slack, as they are exact the "
"same the ticket state colors you'll see in Zammad!"
msgstr ""

#: ../system/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: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 "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 <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 <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 <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:43
msgid ""
"For more details on how S/MIME integration works on the agent side, see the :"
"user-docs:`user docs </extras/secure-email.html>`."
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 ""
"Please note that passphrase-protected private keys stay protected and when "
"you download them, you have to know the passphrase to use them after "
"downloading."
msgstr ""

#: ../system/integrations/smime/manage-certificates.rst:73
msgid "Dialogue to download certificates or private keys"
msgstr ""

#: ../system/integrations/smime/manage-certificates.rst:73
msgid "Download stored certificates and their keys"
msgstr ""

#: ../system/integrations/smime/manage-certificates.rst:78
msgid ""
"The ticket composer will set all outgoing messages to **signed and "
"encrypted** by default (assuming the required certificates exist)."
msgstr ""

#: ../system/integrations/smime/manage-certificates.rst:82
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 behavior on per group basis"
msgstr ""

#: ../system/integrations/smime/manage-certificates.rst:89
msgid ""
"Of course, agents can always manually change these settings on each email "
"they send out."
msgstr ""

#: ../system/integrations/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) <https://sectigo.com/signing-certificates/email-"
"smime-certificate>`_"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:20
msgid "`Secorio <https://secorio.com/en/certificates/smime-email/>`_"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:21
msgid "`GlobalSign <https://shop.globalsign.com/en/secure-email>`_"
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:32
msgid "Certificate and Private Key Checks on Upload"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:34
msgid ""
"The certificate and public key validation is based on the ``X509v3`` "
"extensions."
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:49
msgid "Uploading a *client certificate*?"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:41
msgid "The following attributes are required then:"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:39
msgid "Subject Alternative Name (at least one email address has to be present)"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:40
msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:41
msgid "Public key algorithm (either ``RSA`` or ``EC``)"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:43
msgid ""
"The Extended Key Usage attribute is optional. If the certificate provides "
"the named attribute, than it must contain the value ``E-mail Protection``."
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:46
msgid ""
"Please note that any usable email adress has to be prefixed with ``email:`` "
"or ``rfc822:``."
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:49
msgid "The named public key algorithms are mandatory for private keys as well."
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:54
msgid "Uploading a *CA certificate*?"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:52
msgid ""
"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` "
"in the attribute *Basic Contstraints*, the previously mentioned attributes "
"are not verified."
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:56
msgid ""
"In general, the usage of any expired (``Not After``) or not yet valid (``Not "
"Before``) certificate is denied for outgoing emails."
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:59
msgid "Example certificate:"
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:85
msgid ""
"Please note that Zammad will distrust senders by default. This means that "
"you're always required to provide certificate data, no matter if for signing "
"or encrypting."
msgstr ""

#: ../system/integrations/smime/prerequisites.rst:89
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 </manage/"
"trigger>` or the :doc:`scheduler </manage/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 "
"</manage/trigger>` or the :doc:`scheduler </manage/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 ""
"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\\_<name>**: 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 <https://www.zabbix.com/"
"documentation/current/manual/config/notifications>`_."
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 ""
"This function is only available in self hosted instances. If you use Zammad "
"in our cloud, we are monitoring the system on our own and take steps to fix "
"potential problems directly."
msgstr ""

#: ../system/monitoring.rst:11
msgid ""
"On the monitoring page, you can see the current health state of Zammad under "
"\"*Current Status*\" at the bottom. This can be useful if you want to have a "
"look if everything is up and running. As an example, you could have a look "
"in the monitoring when you assume that some emails aren't processed from "
"Zammad."
msgstr ""

#: ../system/monitoring.rst:17
msgid "**Can't receive an email and the monitoring response is \"healthy\"?**"
msgstr ""

#: ../system/monitoring.rst:19
msgid ""
"Zammad will just inform you about unprocessable emails. This is not the case "
"for oversized emails. You can adjust the maximum email size in :doc:`../"
"channels/email/settings`."
msgstr ""

#: ../system/monitoring.rst:24
msgid "Monitoring API"
msgstr ""

#: ../system/monitoring.rst:26
msgid ""
"Beside the indication in the monitoring page, you can also use an external "
"monitoring tool to monitor Zammad's health. To request the health of Zammad, "
"you need to provide the API key (token) to the external monitoring tool. You "
"can copy the token from the \"*Current Token*\" field as well as the whole "
"API endpoint of your system (\"*Health Check*\" field), in which the API "
"token is already included."
msgstr ""

#: ../system/monitoring.rst:37
msgid "Screenshot showing Current Token and Health Check"
msgstr ""

#: ../system/monitoring.rst:37
msgid "Screenshot showing Token and Health Check"
msgstr ""

#: ../system/monitoring.rst:39
msgid ""
"In addition to that, you can reset the auto-generated token to make sure "
"that already configured monitoring systems won't work anymore. So, please "
"use this \"*Reset*\" button only if you know what you do!"
msgstr ""

#: ../system/monitoring.rst:44
msgid "Example Output"
msgstr ""

#: ../system/monitoring.rst:0
msgid "No issues found"
msgstr ""

#: ../system/monitoring.rst:48 ../system/monitoring.rst:60
msgid "**Indicator in Zammad**:"
msgstr ""

#: ../system/monitoring.rst:0
msgid "Screenshot showing monitoring with no issues"
msgstr ""

#: ../system/monitoring.rst:54 ../system/monitoring.rst:66
msgid "**API response**::"
msgstr ""

#: ../system/monitoring.rst:0
msgid "Issues were found"
msgstr ""

#: ../system/monitoring.rst:0
msgid "Screenshot showing monitoring with issues"
msgstr ""

#: ../system/objects.rst:2
msgid "Objects"
msgstr ""

#: ../system/objects.rst:4
msgid ""
"In Zammad you can add your own fields to tickets, users, organizations and "
"even groups (these are called \"objects\"). This can be useful if you need "
"to add further information to a ticket or any other object in Zammad and the "
"information doesn't fit in any existing field."
msgstr ""

#: ../system/objects.rst:11
msgid ""
"Try to avoid deleting attributes (and disable them instead) as Zammad might "
"run into unexpected conditions if they are referenced somewhere."
msgstr ""

#: ../system/objects.rst:16
msgid ""
"Here's an overview of object attributes. On the upper right you can add new "
"attributes. By default, there will be no custom fields - standard attributes "
"will be grayed out, you can't delete or change those. You can edit custom "
"attributes (they are displayed in black font and have a trash bin on the "
"right side) just by clicking on them."
msgstr ""

#: ../system/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 Attributes"
msgstr ""

#: ../system/objects.rst:42
msgid ""
"Since Zammad introduced :doc:`/system/core-workflows` the need to have a "
"custom positioning for attributes has become more important than ever."
msgstr ""

#: ../system/objects.rst:45
msgid ""
"To adjust the position of such an attribute, simply click on the attribute "
"entry in question, scroll down and adjust the position number. Please note "
"that you cannot change the positioning of default attributes."
msgstr ""

#: ../system/objects.rst:49
msgid ""
"In case two attributes have the same position value, Zammad will sort "
"alphabetically by name automatically."
msgstr ""

#: ../system/objects.rst:None
msgid ""
"Screenshot showing custom attribute entries ordered in between default ones"
msgstr ""

#: ../system/objects.rst:56
msgid "Updating Database After Adding or Editing Attributes"
msgstr ""

#: ../system/objects.rst:58
msgid ""
"When adding or changing attributes, Zammad will not apply the changes "
"instantly, but instead shows you the changed attributes first. If you're "
"ready to go, just click on \"Update Database\" to apply the changes to "
"Zammad. If you made a mistake or just want to discard your changes, click "
"\"Discard changes\"."
msgstr ""

#: ../system/objects.rst:64
msgid ""
"After applying the changes with \"Update Database\", a restart of Zammad is "
"**mandatory**. In most cases, the restart of the service works out of the "
"box (see :docs:`console commands </admin/console/zammad-settings.html>` for "
"more information). However, if your system is configured differently and you "
"don't perform the restart, you may experience unexpected behavior or even "
"errors. You may want to do this kind of configuration during maintenance "
"windows."
msgstr ""

#: ../system/objects.rst:76
msgid ""
"Changes on objects require you to update the database to apply these changes."
msgstr ""

#: ../system/objects.rst:80
msgid "System Attributes"
msgstr ""

#: ../system/objects.rst:82
msgid ""
"Zammad comes with pre-configured attributes. Some of them can't be edited "
"via UI (or at all). This is required for proper operation of Zammad and not "
"a bug."
msgstr ""

#: ../system/objects.rst:88
msgid "Ticket State"
msgstr ""

#: ../system/objects.rst:90
msgid ""
"If the pre-configured states aren't enough for you or you want to change "
"them, you can do so by clicking on the cogwheel icon in the state row in the "
"ticket tab. But you should be careful when changing pre-configured states. "
"This can lead to unwanted behavior in some cases."
msgstr ""

#: ../system/objects.rst:None
msgid "Screenshot showing highlighted ticket state attribute"
msgstr ""

#: ../system/objects.rst:123
msgid "Handling of states"
msgstr ""

#: ../system/objects.rst:100
msgid ""
"In the state configuration screen, you can add new states, disable states or "
"change states."
msgstr ""

#: ../system/objects.rst:0
msgid "Screenshot showing table of default ticket states"
msgstr ""

#: ../system/objects.rst:108
msgid ""
"The `merged` state can't be changed because it is a required system state. "
"Otherwise, the merging of tickets would lead to errors."
msgstr ""

#: ../system/objects.rst:111
msgid ""
"To add a new state, click on the \"New Ticket State\" button in the top "
"right corner. To change an existing state, simply click on the affected "
"state. This opens an edit dialog."
msgstr ""

#: ../system/objects.rst:115
msgid ""
"You can also clone a state or set them to \"Default for new tickets\" or "
"\"Default for follow-ups\" by clicking on the ⁝ action button and select the "
"desired function."
msgstr ""

#: ../system/objects.rst:119
msgid ""
"*Default for new tickets* means that this state is used for every newly "
"created ticket."
msgstr ""

#: ../system/objects.rst:122
msgid ""
"*Default for follow-ups* means that this state is used if the ticket is re-"
"opened after it was closed."
msgstr ""

#: ../system/objects.rst:171
msgid "Ticket state in detail"
msgstr ""

#: ../system/objects.rst:126
msgid ""
"Below you can find a description for each field and option. Please head over "
"to the :ref:`example <example-state>` to see the edit dialog."
msgstr ""

#: ../system/objects.rst:130
msgid ""
"This is the name of the state and what you and your agents are seeing when "
"choosing a state somewhere (e.g. in tickets, trigger configuration)."
msgstr ""

#: ../system/objects.rst:138
msgid ""
"There are different state types you can choose from. By default, Zammad "
"comes with one state per state type."
msgstr ""

#: ../system/objects.rst:141
msgid ""
"**new**: for states for tickets that are new and it hasn't been worked on "
"them"
msgstr ""

#: ../system/objects.rst:143
msgid ""
"**open**: for states for tickets that are in progress and agents are working "
"on them"
msgstr ""

#: ../system/objects.rst:145
msgid ""
"**pending reminder**: for states for tickets that are in progress and you "
"want to set a reminder. (default example: *pending reminder*)"
msgstr ""

#: ../system/objects.rst:147
msgid ""
"**pending action**: for states for tickets that are waiting for a specified "
"time and then change their state (default example: *pending close*)"
msgstr ""

#: ../system/objects.rst:150
msgid ""
"**closed**: for states for tickets that are finished and do not need to be "
"processed further"
msgstr ""

#: ../system/objects.rst:153
msgid ""
"⚠️ Choosing the correct state type is important! If you are in doubt, have a "
"look on the default states and their types!"
msgstr ""

#: ../system/objects.rst:158
msgid "Ignore escalation"
msgstr ""

#: ../system/objects.rst:157
msgid ""
"Here you can define whether tickets of this state will count to escalation "
"time or not."
msgstr ""

#: ../system/objects.rst:161
msgid ""
"You can create a note for the state to inform other admins about the state. "
"This has no effect on tickets."
msgstr ""

#: ../system/objects.rst:165
msgid "Set the state to *active* or *inactive*."
msgstr ""

#: ../system/objects.rst:167
msgid ""
"it is technically possible to set all states to inactive. To keep Zammad "
"working in such a case, the inactive flag of one of the states is ignored."
msgstr ""

#: ../system/objects.rst:194
msgid "Ticket state example"
msgstr ""

#: ../system/objects.rst:174
msgid ""
"Let's assume we want to create a new state which indicates that the ticket "
"has to wait for a response of a third party (e.g. service contractor or "
"manufacturer) and we want to to be able to set a reminder."
msgstr ""

#: ../system/objects.rst:178
msgid ""
"First we give the new state a proper name. In this example we call it "
"\"waiting for manufacturer\"."
msgstr ""

#: ../system/objects.rst:181
msgid ""
"As state type we choose \"pending reminder\". This indicates that the ticket "
"is still open and we can set a reminder. This reminder can be useful if our "
"manufacturer sometimes isn't responding or we want to remind him to give us "
"an answer."
msgstr ""

#: ../system/objects.rst:186
msgid ""
"We choose \"no\" for \"ignore escalation\" because we want to escalate the "
"tickets even if we are waiting on the manufacturer's feedback."
msgstr ""

#: ../system/objects.rst:189
msgid "The **result** in the creation dialog will look like this:"
msgstr ""

#: ../system/objects.rst:0
msgid "Screenshot showing ticket state creation dialog with example"
msgstr ""

#: ../system/objects.rst:199
msgid "Ticket Priority"
msgstr ""

#: ../system/objects.rst:201
msgid ""
"If the pre-configured priorities aren't enough for you or you want to change "
"them, you can do so by clicking on the cogwheel icon in the priority row in "
"the ticket tab:"
msgstr ""

#: ../system/objects.rst:None
msgid "Screenshot showing highlighted ticket priority attribute"
msgstr ""

#: ../system/objects.rst:226
msgid "Handling of priorities"
msgstr ""

#: ../system/objects.rst:210
msgid ""
"In the priority configuration screen, you can add new priorities, disable "
"priorities or change priorities."
msgstr ""

#: ../system/objects.rst:0
msgid "Screenshot showing table of default ticket priorities"
msgstr ""

#: ../system/objects.rst:218
msgid ""
"To add a new priority, click on the \"New Priority\" button in the top right "
"corner. To change an existing priority, simply click on the affected "
"priority. This opens an edit dialog."
msgstr ""

#: ../system/objects.rst:222
msgid ""
"You can also clone a priority or set them to \"Default for new tickets\" by "
"clicking on the ⁝ action button and select the desired function."
msgstr ""

#: ../system/objects.rst:225
msgid ""
"*Default for new tickets* means that this priority is used for every newly "
"created ticket."
msgstr ""

#: ../system/objects.rst:248
msgid "Priorities in detail"
msgstr ""

#: ../system/objects.rst:229
msgid "Below you can find a description for each field and option."
msgstr ""

#: ../system/objects.rst:232
msgid ""
"This is the name of the priority and what you and your agents are seeing "
"when choosing a priority somewhere (e.g. in tickets, trigger configuration)."
msgstr ""

#: ../system/objects.rst:242
msgid "Highlight color"
msgstr ""

#: ../system/objects.rst:237
msgid ""
"Switch between *Low priority* (light blue), *High priority* (red) and - "
"(default). This affects the displayed color for ticket titles in overviews."
msgstr ""

#: ../system/objects.rst:241
msgid "The color options are currently limited to the mentioned options."
msgstr ""

#: ../system/objects.rst:245
msgid ""
"You can create a note for the priority to inform other admins about the "
"priority. This has no effect on tickets."
msgstr ""

#: ../system/objects.rst:249
msgid "Set the priority to *active* or *inactive*."
msgstr ""

#: ../system/objects/external-data-source-example.rst:2
msgid "External Data Source"
msgstr ""

#: ../system/objects/external-data-source-example.rst:4
msgid ""
"We assume you already had a look on :doc:`types` where you can find a "
"description of the individual fields."
msgstr ""

#: ../system/objects/external-data-source-example.rst:7
msgid ""
"To reproduce this example, choose a category you want to add a custom field, "
"click on *New Attribute* and select *External data source field* under "
"*Format*."
msgstr ""

#: ../system/objects/external-data-source-example.rst:11
msgid ""
"Our example story is to fetch data from an external product database. We "
"want to add our products to the tickets so that the products can be searched "
"and chosen from a list and also create a link to the product website."
msgstr ""

#: ../system/objects/external-data-source-example.rst:16
msgid "Base configuration"
msgstr ""

#: ../system/objects/external-data-source-example.rst:None
msgid "Initial steps to configure external data source object type"
msgstr ""

#: ../system/objects/external-data-source-example.rst:25
msgid "Name: *product*"
msgstr ""

#: ../system/objects/external-data-source-example.rst:26
msgid "Display: *Product*"
msgstr ""

#: ../system/objects/external-data-source-example.rst:29
msgid "External data source configuration"
msgstr ""

#: ../system/objects/external-data-source-example.rst:31
msgid ""
"First, enter the search URL making sure it contains ``#{search.term}`` as a "
"parameter:"
msgstr ""

#: ../system/objects/external-data-source-example.rst:34
msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``"
msgstr ""

#: ../system/objects/external-data-source-example.rst:36
msgid ""
"After that, head down to the preview section and enter a search input for "
"the external data source."
msgstr ""

#: ../system/objects/external-data-source-example.rst:39
msgid "**Example:** ``mac``"
msgstr ""

#: ../system/objects/external-data-source-example.rst:41
msgid "Then you can find a preview of the response data below:"
msgstr ""

#: ../system/objects/external-data-source-example.rst:None
msgid "Preview of JSON response based on search term"
msgstr ""

#: ../system/objects/external-data-source-example.rst:48
msgid ""
"We recommend using the preview to have a look on the structure. There is a "
"top-level element called ``products``. One level below, you can find the "
"attributes ``id`` and ``title``."
msgstr ""

#: ../system/objects/external-data-source-example.rst:52
msgid "**Search result response based on search from example:**"
msgstr ""

#: ../system/objects/external-data-source-example.rst:119
msgid ""
"To tell the remote system that the desired data is located below the "
"``products`` level, you have to put it in the field *Search result list key*."
msgstr ""

#: ../system/objects/external-data-source-example.rst:122
msgid ""
"After inserting ``products`` in the mentioned field, you get an extended "
"preview. You can find an additional box *Search result list* with a JSON "
"structure. This is the same response as before but stripped from the upper "
"``products`` element by the external data source."
msgstr ""

#: ../system/objects/external-data-source-example.rst:None
msgid "Preview of JSON response search result list"
msgstr ""

#: ../system/objects/external-data-source-example.rst:132
msgid ""
"Now you need to provide the keys for the search result values and labels. As "
"already mentioned, we are looking for the ``id`` and the ``title`` of our "
"products. If you haven't already, it is now a good time to look at the "
"preview of the *Search result list*."
msgstr ""

#: ../system/objects/external-data-source-example.rst:197
msgid ""
"After locating our two keys, we insert them in *search result value key* "
"(``id``) and in *Search result label key* (``title``)."
msgstr ""

#: ../system/objects/external-data-source-example.rst:200
msgid ""
"Basically, we configured the external data source already and we can see a "
"table in the preview section:"
msgstr ""

#: ../system/objects/external-data-source-example.rst:None
msgid "Preview of product table based on search term"
msgstr ""

#: ../system/objects/external-data-source-example.rst:208
msgid ""
"According to our example story, now just the *Link template* is missing."
msgstr ""

#: ../system/objects/external-data-source-example.rst:210
msgid ""
"Please note that this is an optional feature. If you don't want to use such "
"links, of course you don't have to configure it."
msgstr ""

#: ../system/objects/external-data-source-example.rst:213
msgid ""
"We can add now an address where additional product information can be found."
msgstr ""

#: ../system/objects/external-data-source-example.rst:215
msgid "Example: ``https://your_domain.com/q=#{ticket.product}``"
msgstr ""

#: ../system/objects/external-data-source-example.rst:217
msgid "In the example, the parameter means:"
msgstr ""

#: ../system/objects/external-data-source-example.rst:219
msgid "``#{}``: \"Frame\" for the insertion of information"
msgstr ""

#: ../system/objects/external-data-source-example.rst:220
msgid "``ticket``: object level, where you create your custom object"
msgstr ""

#: ../system/objects/external-data-source-example.rst:221
msgid "``product``: name of the (custom) object"
msgstr ""

#: ../system/objects/external-data-source-example.rst:223
msgid ""
"After configuring your *Link template*, there will be another column in the "
"preview. Hovering on the icons in the *Link* column will show you where it "
"forwards you."
msgstr ""

#: ../system/objects/external-data-source-example.rst:232
msgid ""
"In our example, one of the links looks like: https://your_domain.com/q=6, "
"where the 6 is the product id."
msgstr ""

#: ../system/objects/external-data-source-example.rst:235
msgid "You can find more information regarding the URL in :doc:`types`."
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 field type allows the positioning of its values ↔️**"
msgstr ""

#: ../system/objects/includes/reposition-treeselect-values.include.rst:3
msgid ""
"In order to re-arrange the field values, first edit the field. Then you can "
"use ☰ to drag the values in question to the correct position. If you want to "
"change the layer depth, double click on ☰. With it you can cycle through the "
"available layers."
msgstr ""

#: ../system/objects/includes/reposition-treeselect-values.include.rst:8
msgid "When you're ready, submit your changes to save the object attribute."
msgstr ""

#: :0 ../system/objects/types.rst:0
msgid ""
"Screencast showing how to re-position values on tree select like\n"
"fields"
msgstr ""

#: ../system/objects/includes/reposition-values.include.rst:3
msgid ""
"In order to re-arrange the field values, edit the field and scroll below the "
"values. Make sure to tick the option \"Use custom option sort\"."
msgstr ""

#: ../system/objects/includes/reposition-values.include.rst:8
msgid ""
"If you do not tick this field, all manual positioning you did above will be "
"lost upon saving! ☠️"
msgstr ""

#: ../system/objects/includes/reposition-values.include.rst:11
msgid ""
"Now use ☰ to drag the values in question to the correct position. When "
"you're ready, submit your changes to save the object attribute."
msgstr ""

#: :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) <link-templates>`."
msgstr ""

#: ../system/objects/permissions.rst:2
msgid "Attribute Permissions"
msgstr ""

#: ../system/objects/permissions.rst:7
msgid ""
"In the object attributes configuration you can define if a field is shown "
"and if the input in the field is mandatory, separated by different screens "
"and for different :doc:`roles/permissions </manage/roles/index>`."
msgstr ""

#: ../system/objects/permissions.rst:17
msgid "Screenshot shows object attribute permission table"
msgstr ""

#: ../system/objects/permissions.rst:17
msgid ""
"Some of the possible permissions and screen options for a user object "
"attribute."
msgstr ""

#: ../system/objects/permissions.rst:19
msgid ""
"Based on the object context (ticket, agent, organization, user), the "
"selectable roles (to be precise: the required permissions) and screens "
"differ. Be aware that these settings aren't affecting data creation via "
"other channels than the UI."
msgstr ""

#: ../system/objects/permissions.rst:24
msgid ""
"If you want to have further customization possibilities, you should have a "
"look at the :doc:`core workflows </system/core-workflows>`."
msgstr ""

#: ../system/objects/permissions.rst:28
msgid "Screens"
msgstr ""

#: ../system/objects/permissions.rst:30
msgid ""
"In the table below you can find an overview about the different permissions "
"and the available screens Zammad distinguishes between."
msgstr ""

#: ../system/objects/permissions.rst:37
msgid "Screen"
msgstr ""

#: ../system/objects/permissions.rst:38
msgid "Available for"
msgstr ""

#: ../system/objects/permissions.rst:40
msgid "create"
msgstr ""

#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52
#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73
msgid "admin.user"
msgstr ""

#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53
#: ../system/objects/permissions.rst:60
msgid "admin.organization"
msgstr ""

#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54
#: ../system/objects/permissions.rst:61
msgid "admin.group"
msgstr ""

#: ../system/objects/permissions.rst:44
msgid "Creation dialog for not yet existing data"
msgstr ""

#: ../system/objects/permissions.rst:45
msgid "create_middle"
msgstr ""

#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50
#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66
#: ../system/objects/permissions.rst:70
msgid "ticket.customer"
msgstr ""

#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51
#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69
msgid "ticket.agent"
msgstr ""

#: ../system/objects/permissions.rst:48
msgid "Ticket create dialog (middle section)"
msgstr ""

#: ../system/objects/permissions.rst:49
msgid "edit"
msgstr ""

#: ../system/objects/permissions.rst:55
msgid "Editing dialog for already existing data"
msgstr ""

#: ../system/objects/permissions.rst:56
msgid "view"
msgstr ""

#: ../system/objects/permissions.rst:62
msgid "View-only dialog for already existing data"
msgstr ""

#: ../system/objects/permissions.rst:64
msgid "(e.g. user or organization from search)"
msgstr ""

#: ../system/objects/permissions.rst:65
msgid "signup"
msgstr ""

#: ../system/objects/permissions.rst:67
msgid "Sign-up screen for new customers"
msgstr ""

#: ../system/objects/permissions.rst:68
msgid "invite_customer"
msgstr ""

#: ../system/objects/permissions.rst:71
msgid ""
"Customer invitation screen (from :doc:`First Steps </misc/first-steps>` area)"
msgstr ""

#: ../system/objects/permissions.rst:72
msgid "invite_agent"
msgstr ""

#: ../system/objects/permissions.rst:74
msgid ""
"Agent invitation screen (from :doc:`First Steps </misc/first-steps>` area)"
msgstr ""

#: ../system/objects/permissions.rst:78
msgid "Screen Options"
msgstr ""

#: ../system/objects/permissions.rst:80
msgid ""
"For the different screens you can select \"show\" and \"required\" options."
msgstr ""

#: ../system/objects/permissions.rst:82
msgid "**shown:** Show (check) or hide (uncheck) a field."
msgstr ""

#: ../system/objects/permissions.rst:83
msgid ""
"**required:** Set a field to mandatory (check). Forces users (via UI and "
"API) to populate the field."
msgstr ""

#: ../system/objects/types.rst:7
msgid "Example external data source"
msgstr ""

#: ../system/objects/types.rst:2
msgid "Attribute types"
msgstr ""

#: ../system/objects/types.rst:4
msgid ""
"When adding a new object attribute, you can choose between the following "
"attribute types."
msgstr ""

#: ../system/objects/types.rst:14
msgid ""
"You cannot change the attribute format / type as soon as it is applied. If "
"you no longer need an object attribute, consider disabling it instead of "
"removing."
msgstr ""

#: ../system/objects/types.rst:18
msgid "**What about the translation of my attributes?**"
msgstr ""

#: ../system/objects/types.rst:20
msgid ""
"For some attribute types you can decide if they should be translatable or "
"not. To be precise, it works only for the selectable fields because the "
"possible choices are known and limited. For the following attribute types, "
"you can set the translatable flag:"
msgstr ""

#: ../system/objects/types.rst:25
msgid "*Boolean field*"
msgstr ""

#: ../system/objects/types.rst:26
msgid "*Single selection field*"
msgstr ""

#: ../system/objects/types.rst:27
msgid "*Multiple selection field*"
msgstr ""

#: ../system/objects/types.rst:28
msgid "*Single tree selection field*"
msgstr ""

#: ../system/objects/types.rst:29
msgid "*Multiple tree selection field*"
msgstr ""

#: ../system/objects/types.rst:31
msgid ""
"For these types, you can find an additional field *Translate field contents*:"
msgstr ""

#: ../system/objects/types.rst:0
msgid "Screenshot showing translatable attribute types"
msgstr ""

#: ../system/objects/types.rst:38
msgid "Screenshot with example of translatable attribute type"
msgstr ""

#: ../system/objects/types.rst:45
msgid "Boolean field"
msgstr ""

#: ../system/objects/types.rst:41
msgid ""
"Provides a drop-down field with display values for ``true`` and ``false``. "
"Setting a default is mandatory."
msgstr ""

#: ../system/objects/types.rst:0
msgid "Available settings for Boolean fields"
msgstr ""

#: ../system/objects/types.rst:55
msgid "Date field"
msgstr ""

#: ../system/objects/types.rst:48
msgid "Provides a date picker field and does not allow default values."
msgstr ""

#: ../system/objects/types.rst:52
msgid "Default time diff (hours)"
msgstr ""

#: ../system/objects/types.rst:51
msgid ""
"This setting helps the user by highlighting the day from now plus the "
"provided value. It *does not* pre-fill the field."
msgstr ""

#: ../system/objects/types.rst:0
msgid "Available settings for Date fields"
msgstr ""

#: ../system/objects/types.rst:73
msgid "Date & time field"
msgstr ""

#: ../system/objects/types.rst:58
msgid "Provides a date and time picker – does not allow default values"
msgstr ""

#: ../system/objects/types.rst:62
msgid "Allow future"
msgstr ""

#: ../system/objects/types.rst:0
msgid "Forbid dates and times in the future."
msgstr ""

#: ../system/objects/types.rst:66
msgid "Allow past"
msgstr ""

#: ../system/objects/types.rst:0
msgid "Forbid dates and times in the past."
msgstr ""

#: ../system/objects/types.rst:70
msgid "Default time diff (minutes)"
msgstr ""

#: ../system/objects/types.rst:69
msgid ""
"This setting helps the user by highlighting the day from now plus the "
"provided value. It does not pre-fill the field."
msgstr ""

#: ../system/objects/types.rst:0
msgid "Available settings for Date & time fields"
msgstr ""

#: ../system/objects/types.rst:86
msgid "Integer field"
msgstr ""

#: ../system/objects/types.rst:76
msgid ""
"Provides an input field that allows integer usage only. You may define a "
"default value. You cannot enforce comma separation."
msgstr ""

#: ../system/objects/types.rst:80
msgid "Minimal"
msgstr ""

#: ../system/objects/types.rst:80
msgid "The minimal value the field accepts."
msgstr ""

#: ../system/objects/types.rst:83
msgid "Maximal"
msgstr ""

#: ../system/objects/types.rst:83
msgid "The maximum value the field accepts."
msgstr ""

#: ../system/objects/types.rst:0
msgid "Available settings for Integer fields"
msgstr ""

#: ../system/objects/types.rst:99
msgid "Multiple selection field"
msgstr ""

#: ../system/objects/types.rst:89
msgid ""
"Provides a selection field that allows the selection of one or more out of "
"several. This field does allow setting a default value."
msgstr ""

#: ../system/objects/types.rst:0
msgid "Available settings for Multiple selection fields"
msgstr ""

#: ../system/objects/types.rst:112
msgid "Single selection field"
msgstr ""

#: ../system/objects/types.rst:102
msgid ""
"Provides a drop-down field that allows selection of one value out of "
"several. This field does allow setting a default value."
msgstr ""

#: ../system/objects/types.rst:0
msgid "Available settings for Single selection fields"
msgstr ""

#: ../system/objects/types.rst:142
msgid "Textarea field"
msgstr ""

#: ../system/objects/types.rst:115
msgid ""
"Provides a text area input field (multiple lines) and thus allows e.g. new "
"lines. You can set a default field value."
msgstr ""

#: ../system/objects/types.rst:120
msgid ""
"Please note that this field *does not* support text formatting or HTML "
"content (rich text)."
msgstr ""

#: ../system/objects/types.rst:123
msgid "**🥵 This field can consume a lot of visual space**"
msgstr ""

#: ../system/objects/types.rst:125
msgid ""
"Depending on where you use this field type, it may use a lot of visual space "
"if you provide a lot of text. This may be an issue to work with."
msgstr ""

#: ../system/objects/types.rst:130
msgid "Default"
msgstr ""

#: ../system/objects/types.rst:129
msgid ""
"The here provided text will be shown within the text area field or new data "
"sets."
msgstr ""

#: ../system/objects/types.rst:134 ../system/objects/types.rst:160
msgid "Maxlength"
msgstr ""

#: ../system/objects/types.rst:0 ../system/objects/types.rst:160
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:139
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:165
msgid "Text field"
msgstr ""

#: ../system/objects/types.rst:145
msgid "Provides a text field (one line) and allows choosing a default value."
msgstr ""

#: ../system/objects/types.rst:148
msgid ""
"Defines the type of the input field. This allows e.g. your browser to ensure "
"that you provide the specific type."
msgstr ""

#: ../system/objects/types.rst:152
msgid "Currently available:"
msgstr ""

#: ../system/objects/types.rst:155
msgid "Phone"
msgstr ""

#: ../system/objects/types.rst:156
msgid "Text"
msgstr ""

#: ../system/objects/types.rst:157
msgid "Url *(URL fields disable link-template availability)*"
msgstr ""

#: ../system/objects/types.rst:0
msgid "Available settings for Text fields"
msgstr ""

#: ../system/objects/types.rst:174
msgid "Single tree selection field"
msgstr ""

#: ../system/objects/types.rst:168
msgid ""
"Provides a select-like field with up to 6 layers of options. Does not allow "
"setting a default value."
msgstr ""

#: ../system/objects/types.rst:0
msgid "Available settings for Tree Select fields"
msgstr ""

#: ../system/objects/types.rst:183
msgid "Multiple tree selection field"
msgstr ""

#: ../system/objects/types.rst:177
msgid ""
"Provides a select-like field with up to 6 layers of options allowing the "
"selection of multiple values. Does not allow setting a default value."
msgstr ""

#: ../system/objects/types.rst:302
msgid "External Data Source field"
msgstr ""

#: ../system/objects/types.rst:186
msgid ""
"Provides a searchable field which fetches data from an external system. This "
"can be useful if you have data outside of Zammad and don't want to maintain "
"both data sources."
msgstr ""

#: ../system/objects/types.rst:190
msgid "The feature works as follows:"
msgstr ""

#: ../system/objects/types.rst:192
msgid ""
"Zammad sends a query with a search string (free text from agent or based on "
"a variable) in a pre-defined format (\"Search URL\") to an external system."
msgstr ""

#: ../system/objects/types.rst:195
msgid ""
"This external system searches for matches and provides a response as a JSON "
"structure to Zammad."
msgstr ""

#: ../system/objects/types.rst:197
msgid ""
"Zammad just looks for the defined list and value keys, reads the content and "
"displays the value to the user. There is no search on Zammad side."
msgstr ""

#: ../system/objects/types.rst:201
msgid ""
"The usage of a PostgreSQL database for Zammad is required. In any other "
"case, Zammad will hide the external data source type and you are not able to "
"use it. If you want to use this feature, consider to :docs:`migrate your "
"database </appendix/migrate-to-postgresql.html>`."
msgstr ""

#: ../system/objects/types.rst:205
msgid "Currently, only ``GET`` is supported as request method."
msgstr ""

#: ../system/objects/types.rst:206
msgid ""
"The data structure must be in JSON format and provide the objects in an "
"array."
msgstr ""

#: ../system/objects/types.rst:208
msgid ""
"The endpoint for the external data source has to support search. On Zammad "
"side, there is no search/logic implemented; however, you can define the "
"output key and value based on the result(s) from the response (which "
"provides already filtered content based on the search)."
msgstr ""

#: ../system/objects/types.rst:212
msgid ""
"If you receive more results as expected, your external data source search "
"may not work properly or the structure of the URL is not correct. You should "
"get in touch with a responsible person from the external system."
msgstr ""

#: ../system/objects/types.rst:217
msgid ""
"Please have a look :doc:`at our example </system/objects/external-data-"
"source-example>`, where you can find a possible configuration for a public "
"dummy endpoint."
msgstr ""

#: ../system/objects/types.rst:0
msgid "Available settings for external data source fields"
msgstr ""

#: ../system/objects/types.rst:242
msgid "Search URL"
msgstr ""

#: ../system/objects/types.rst:227
msgid ""
"Set your endpoint where Zammad fetches the data. Please make sure to include "
"a valid search :doc:`variable </misc/variables>` as an URL parameter. "
"Example for a free text search at user input: ``#{search.term}``"
msgstr ""

#: ../system/objects/types.rst:232
msgid ""
"If in doubt, ask the responsible person for the external data source how "
"they expect the structure of the URL."
msgstr ""

#: ../system/objects/types.rst:236
msgid ""
"Depending on your search variable, the preview might work or not. The reason "
"is that the context might not be available and it is no bug."
msgstr ""

#: ../system/objects/types.rst:239
msgid ""
"Please also make sure to use a variable which is available in your object "
"context. For example you won't be able to search for a ticket in a user "
"object context."
msgstr ""

#: ../system/objects/types.rst:252
msgid "SSL Verification"
msgstr ""

#: ../system/objects/types.rst:245
msgid "Here you can switch the SSL verification to no."
msgstr ""

#: ../system/objects/types.rst:249
msgid ""
"If your external data source system is using self signed certificates, "
"please have a look :doc:`here </settings/security/ssl-certificates>` for "
"further information about how to handle them in Zammad, so you can keep the "
"SSL verification activated."
msgstr ""

#: ../system/objects/types.rst:258
msgid "HTTP Authentication"
msgstr ""

#: ../system/objects/types.rst:255
msgid ""
"If your external data source requires an authentication, you can set it "
"here. You can leave it empty or choose between *Basic Authentication* or "
"*Authentication Token* (selecting one of the two methods leads to additional "
"fields where you can enter your credentials/token)."
msgstr ""

#: ../system/objects/types.rst:265
msgid "Search result list key"
msgstr ""

#: ../system/objects/types.rst:261
msgid ""
"Defines the level in the JSON structure which provides the list with search "
"results. You can leave it empty, if the data is already provided as an "
"array. If you have to go deeper in the structure, you can provide a path "
"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``."
msgstr ""

#: ../system/objects/types.rst:271
msgid "Search result value key"
msgstr ""

#: ../system/objects/types.rst:268
msgid ""
"Defines the attribute in the structure in which your external data source "
"provides the *value* for your data. An example would be a product *number*. "
"If you have to go deeper in the structure, you can provide a path with ``.`` "
"as separators, e.g. ``key.subkey.sub-sub-key``."
msgstr ""

#: ../system/objects/types.rst:277
msgid "Search result label key"
msgstr ""

#: ../system/objects/types.rst:274
msgid ""
"Defines the attribute in the structure in which your external data source "
"provides the *label* for your data. An example would be a product *name*. If "
"you have to go deeper in the structure, you can provide a path with ``.`` as "
"separators, e.g. ``key.subkey.sub-sub-key``."
msgstr ""

#: ../system/objects/types.rst:280
msgid ""
"In the preview area, you can find the following items (depending on your "
"configuration above):"
msgstr ""

#: ../system/objects/types.rst:283
msgid ""
"**Error/hint message** (only if configuration is not complete): Zammad tells "
"you, if there is a problem and what you should change in your configuration."
msgstr ""

#: ../system/objects/types.rst:286
msgid ""
"**Search field**: search for an existing attribute in the data source to get "
"a preview. This is required for the fields below to show up."
msgstr ""

#: ../system/objects/types.rst:288
msgid ""
"**Search result response** (only if configuration is not complete): here you "
"can find a syntax highlighted JSON preview of the response, based on the "
"search term you entered."
msgstr ""

#: ../system/objects/types.rst:291
msgid ""
"**Search result list** (only if *search result list key* is properly set): "
"output of the structure under the configured *search result list key*."
msgstr ""

#: ../system/objects/types.rst:294
msgid ""
"**Preview table** (when fully configured): Zammad shows you a table which "
"includes the found items based on the search string (value, label and "
"optional link). You can use this preview if you don't have the complete data "
"structure of the external system in mind."
msgstr ""

#: ../system/objects/types.rst:299
msgid ""
"An example of a configured external data source field from agent perspective:"
msgstr ""

#: ../system/objects/types.rst:0
msgid "Screencast showing the search for a product in a ticket"
msgstr ""

#: ../system/objects/types.rst:307
msgid "URL fields (Link-Template)"
msgstr ""

#: ../system/objects/types.rst:311
msgid ""
"This function is restricted to Text, Select and External data source types "
"only."
msgstr ""

#: ../system/objects/types.rst:314
msgid ""
"Link-Templates are an amazing way to dynamically generate URLs. They allow "
"you to integrate other systems better without having to manually copy data "
"from Zammad if possible."
msgstr ""

#: ../system/objects/types.rst:320
msgid ""
"Another great way of communicating with another system may be Zammad's :doc:"
"`Webhooks </manage/webhook>`."
msgstr ""

#: ../system/objects/types.rst:323
msgid ""
"After filling a link-template enabled field, an URL icon will appear on its "
"right. Clicking on the icon opens a new tab."
msgstr ""

#: ../system/objects/types.rst:328
msgid ""
"Even though Zammad displays the link template within object edit and create "
"screens, the function is optional. It's only active if you populate the "
"field."
msgstr ""

#: ../system/objects/types.rst:333
msgid ""
"What's the difference between URL and text fields with link template...?!"
msgstr ""

#: ../system/objects/types.rst:335
msgid ""
"Both fields have different use cases. Use ``text`` type text fields when "
"ever you have a *static* url that requires dynamic parameters. If you "
"require a drag & drop like field that you can put in any URL, use ``URL`` "
"type text fields."
msgstr ""

#: ../system/objects/types.rst:340
msgid ""
"The difference is easier to spot when comparing the fields directly, below "
"screencast shows the result - the dynamic approach uses existing values in "
"the moment of updating to built the URL - e.g. ``https://google.com/search?"
"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. "
"``https://zammad.com``."
msgstr ""

#: ../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:352
msgid "How does this work...?!"
msgstr ""

#: ../system/objects/types.rst:354
msgid ""
"As an example, let's say you have an attribute called ``amazing_attribute`` "
"and you want to open a google search directly with the input from that field."
msgstr ""

#: ../system/objects/types.rst:357
msgid ""
"Providing the link-template field below allows you to do so: ``https://www."
"google.com/search?q=#{ticket.amazing_attribute}``"
msgstr ""

#: ../system/objects/types.rst:362
msgid ""
"You can use any :doc:`Zammad variable </misc/variables>` as long as it's "
"available in the moment you need it."
msgstr ""

#: ../system/objects/types.rst:365
msgid ""
"As a result, you are redirected to Google with a search for the value of the "
"attribute, if you click on the button in the ticket (as you can see in the "
"screencast above)."
msgstr ""

#: ../system/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. The session timeout is affected by :ref:"
"`security_session_timeout` configurations from security settings."
msgstr ""

#: ../system/sessions.rst:None
msgid "Screenshot showing Zammad's session management"
msgstr ""

#: ../system/sessions.rst:13
msgid "Zammad will provide the following information:"
msgstr ""

#: ../system/sessions.rst:16
msgid ""
"The user account this session entry belongs to. It can be normal if a user "
"has several sessions in the list. This can be due to changed browser "
"information or if you use e.g. single sign on methods where the user does "
"not use the log off button."
msgstr ""

#: ../system/sessions.rst:22
msgid "Browser"
msgstr ""

#: ../system/sessions.rst:22
msgid "The browser agent communicated to Zammad."
msgstr ""

#: ../system/sessions.rst:40
msgid "Location"
msgstr ""

#: ../system/sessions.rst:25
msgid ""
"The anticipated location based on the users IP address. Depending on the IP "
"address the result shown may differ. This option depends on :doc:`/settings/"
"system/services`."
msgstr ""

#: ../system/sessions.rst:29
msgid "The following information can be shown:"
msgstr ""

#: ../system/sessions.rst:33
msgid "IP address"
msgstr ""

#: ../system/sessions.rst:32
msgid ""
"Either if you set *Geo IP services* to inactive or you're using internal IP "
"address which do not provide location information."
msgstr ""

#: ../system/sessions.rst:40
msgid "Country (or Country + City)"
msgstr ""

#: ../system/sessions.rst:36
msgid ""
"If *Geo IP services* is enabled only. Depends on how detailed the available "
"IP address information are."
msgstr ""

#: ../system/sessions.rst:39
msgid ""
"Be aware that results can be inaccurate - this technically is not an error."
msgstr ""

#: ../system/sessions.rst:43
msgid "Age"
msgstr ""

#: ../system/sessions.rst:43
msgid "Provides the time when the session initially has been created."
msgstr ""

#: ../system/sessions.rst:50
msgid "Update"
msgstr ""

#: ../system/sessions.rst:46
msgid ""
"Provides the time the user used this session to open Zammad. This timestamp "
"is only updated if the user e.g. reloads, not during normal work on tickets."
msgstr ""

#: ../system/sessions.rst:50
msgid "This timestamp is being used for the session timeout."
msgstr ""

#: ../system/sessions.rst:53
msgid ""
"Use the delete button to remove a single session on behalf of your user."
msgstr ""

#: ../system/subscription.rst:2
msgid "Subscription (SaaS)"
msgstr ""

#: ../system/subscription.rst:4
msgid ""
"The subscription settings page allows you to configure your instances "
"package and number of agents required."
msgstr ""

#: ../system/subscription.rst:9
msgid ""
"This setting section is only available for Hosted setups. If you're looking "
"for on premise support contracts, please see the `Zammad pricing page "
"<https://zammad.com/en/pricing#selfhosted>`_."
msgstr ""

#: ../system/subscription.rst:14 ../system/subscription.rst:34
msgid "Plan"
msgstr ""

#: ../system/subscription.rst:16
msgid ""
"Here you can set up everything affecting your instance subscription "
"functions like number of agents and package."
msgstr ""

#: ../system/subscription.rst:19
msgid ""
"On top of the page you can find a subscription summary. You'll find the "
"number of used and available (booked) agent seats there. By using the *see "
"more* link you can also expand an agent list to see the currently configured "
"active agents. This list *does not* count accounts with admin permissions "
"only."
msgstr ""

#: ../system/subscription.rst:None
msgid ""
"Within subscription you can always see how many agents are still\n"
"available to add and who uses the seats."
msgstr ""

#: ../system/subscription.rst:29
msgid ""
"Learn more on how to manage your agents in general :doc:`here </manage/users/"
"index>`."
msgstr ""

#: ../system/subscription.rst:36
msgid ""
"This section gives you an overview of the available plans and their "
"functions / limits. If you require a more detailed table, check our "
"`detailed pricing table <https://zammad.com/en/pricing/table>`_ for more."
msgstr ""

#: ../system/subscription.rst:40
msgid ""
"Your selection in this step will decide on the base agent price and e.g. "
"agent limits that might apply in the summary step."
msgstr ""

#: ../system/subscription.rst:43
msgid ""
"The green *Selected* button will also tell you what plan you're currently in."
msgstr ""

#: ../system/subscription.rst:47
msgid ""
"Trial instances are running at Professional with 3 agents. The plan cannot "
"be changed during the trial for technical reasons, if you require more "
"agents for testing, please contact `our sales team <https://zammad.com/en/"
"company/contact>`_ with a reason for the raise request."
msgstr ""

#: ../system/subscription.rst:None
msgid ""
"Screenshot showing three available packages for a hosted Zammad\n"
"instance"
msgstr ""

#: ../system/subscription.rst:57
msgid ""
"At the bottom of this block you can find a summary where you can adjust the "
"settings of the previous selected plan."
msgstr ""

#: ../system/subscription.rst:62
msgid ""
"Note that upgrading (more agents, higher package) is always possible, "
"however, downgrading will only happen when your billing period renews."
msgstr ""

#: ../system/subscription.rst:66
msgid ""
"Upgrading resets your billing period and existing credit will be deducted "
"from the new total."
msgstr ""

#: ../system/subscription.rst:75
msgid "Billing cycle"
msgstr ""

#: ../system/subscription.rst:70
msgid ""
"You can choose between either monthly or yearly billing. The price per agent "
"will be cheaper if you decide for yearly billing."
msgstr ""

#: ../system/subscription.rst:73
msgid ""
"If you're still trying out things and are unsure of the right package for "
"your instance, you may want to choose monthly first and then upgrade to "
"yearly when you're sure."
msgstr ""

#: ../system/subscription.rst:83
msgid "Plan: (Starter|Professional|Plus) - Agents"
msgstr ""

#: ../system/subscription.rst:78
msgid "Choose the number of agents you require for your instance."
msgstr ""

#: ../system/subscription.rst:80
msgid ""
"Keep in mind that some packages may have agent limits. Depending on the "
"previous chosen package, you won't be able to exceed specific agent numbers. "
"Also note that setting less agents than currently configured is not possible."
msgstr ""

#: ../system/subscription.rst:86
msgid "Total"
msgstr ""

#: ../system/subscription.rst:86
msgid "This will be the net total you're going to be billed."
msgstr ""

#: ../system/subscription.rst:88
msgid ""
"By using the *Update subscription* button, the instance package will be "
"adjusted immediately. If you didn't provide a payment method yet, Zammad "
"will request you to provide one at this point."
msgstr ""

#: ../system/subscription.rst:94
msgid ""
"In case you're still within the trial period, this means that the trial will "
"be over immediately!"
msgstr ""

#: ../system/subscription.rst:97
msgid "Down- or upgrading during the trial period *is not* possible."
msgstr ""

#: ../system/subscription.rst:None
msgid "Screenshot showing payment options and a pricing summary"
msgstr ""

#: ../system/subscription.rst:103
msgid "Billing Information"
msgstr ""

#: ../system/subscription.rst:105
msgid ""
"You can control all billing relevant information like invoices and the "
"billing address."
msgstr ""

#: ../system/subscription.rst:108
msgid ""
"All adjusted billing information below only affect future invoices. If your "
"invoice was issued wrong, please contact `our sales team <https://zammad.com/"
"en/company/contact>`_."
msgstr ""

#: ../system/subscription.rst:114
msgid "Billing address"
msgstr ""

#: ../system/subscription.rst:113
msgid ""
"Provide your company address here, make sure to include the name of the "
"company in case required. This address will be referenced on your invoice."
msgstr ""

#: ../system/subscription.rst:118
msgid "VAT ID"
msgstr ""

#: ../system/subscription.rst:117
msgid ""
"Provide your VAT ID here. If applicable your invoice will not contain German "
"VAT. Please make sure to pay the VAT in your country as required."
msgstr ""

#: ../system/subscription.rst:127
msgid "Billing Email Address"
msgstr ""

#: ../system/subscription.rst:121
msgid ""
"Usually the instance owner (the person that registered the instance) will "
"receive all emails including the invoices. In case you have your own billing "
"department, you can provide their email address here."
msgstr ""

#: ../system/subscription.rst:125
msgid ""
"All billing relevant information will then be sent to this email address."
msgstr ""

#: ../system/subscription.rst:127
msgid "Invoices are sent as attachment (PDF) to this email address."
msgstr ""

#: ../system/subscription.rst:129
msgid ""
"Don't forget to press the *Update billing information* button after you "
"changed above settings."
msgstr ""

#: ../system/subscription.rst:None
msgid ""
"Screenshot showing options for billing information within the\n"
"subscription menu"
msgstr ""

#: ../system/subscription.rst:137
msgid "Payment Method"
msgstr ""

#: ../system/subscription.rst:139
msgid "You can pay via credit card or SEPA mandate."
msgstr ""

#: ../system/subscription.rst:144
msgid "Credit card"
msgstr ""

#: ../system/subscription.rst:142
msgid ""
"Simply follow the dialogue by clicking *authorize credit card* and confirm -"
"if required by your bank- your consent to Zammad using your card for the "
"payments."
msgstr ""

#: ../system/subscription.rst:148
msgid "SEPA Direct Debit"
msgstr ""

#: ../system/subscription.rst:147
msgid ""
"Provide the requested information of the bank account holder and update if "
"you're ready. You'll then receive an email with the SEPA mandate."
msgstr ""

#: ../system/subscription.rst:150
msgid ""
"Technically there's also the possibility to pay via invoice, however - this "
"method only applies to a fairly low number of instances. Please contact `our "
"sales team <https://zammad.com/en/company/contact>`_ for more information."
msgstr ""

#: ../system/subscription.rst:156
msgid "Cancel Subscription"
msgstr ""

#: ../system/subscription.rst:158
msgid ""
"Do you want to cancel your subscription? In case you no longer want to use "
"Zammad's SaaS, you can cancel your subscription by using the red *Yes, "
"please cancel my subscription* button."
msgstr ""

#: ../system/subscription.rst:162
msgid ""
"To cancel the subscription, enter the FQDN of your Zammad instance and "
"provide a reason for your cancellation."
msgstr ""

#: ../system/subscription.rst:165
msgid ""
"Your subscription will end the day after your trial or billing period ends."
msgstr ""

#: ../system/subscription.rst:None
msgid "Screenshot showing subscription cancellation dialog"
msgstr ""

#: ../system/subscription.rst:174
msgid ""
"We will remind you about your cancelled subscription several times up front. "
"After the subscription ended all instance data will be removed. A restore "
"*is not* possible after that point!"
msgstr ""

#: ../system/subscription.rst:178
msgid "**😖 Cancelled by accident?**"
msgstr ""

#: ../system/subscription.rst:180
msgid ""
"You can always undo the cancellation via the *Yes, undo the cancellation of "
"my subscription* button up to the last subscription day!"
msgstr ""

#: ../system/subscription.rst:0
msgid ""
"Screenshot showing a red button to cancel the subscription\n"
"cancellation"
msgstr ""

#: ../system/subscription.rst:189
msgid "Payment History"
msgstr ""

#: ../system/subscription.rst:191
msgid ""
"The payment history will display a history of all paid invoices. At this "
"point you can also download these in case you need them again."
msgstr ""

#: ../system/subscription.rst:196
msgid ""
"You will only find *paid* invoices here. Invoices that are to be billed are "
"not available before the payment is completed."
msgstr ""

#: ../system/subscription.rst:201
msgid "Date"
msgstr ""

#: ../system/subscription.rst:201
msgid "Date of the invoice creation."
msgstr ""

#: ../system/subscription.rst:204
msgid "Amount"
msgstr ""

#: ../system/subscription.rst:204
msgid "Invoice total including VAT if applicable."
msgstr ""

#: ../system/subscription.rst:207
msgid ""
"Contains contract period (monthly or yearly) and hosted plan for the "
"subscription period in question."
msgstr ""

#: ../system/subscription.rst:218
msgid "Payment method / Service period"
msgstr ""

#: ../system/subscription.rst:211
msgid ""
"Used bank account or credit card as well as the subscription period the "
"invoice is about."
msgstr ""

#: ../system/subscription.rst:216
msgid ""
"It might happen that the invoice date and subscription period differ. This "
"is nothing to worry about, the subscription periods will be accounted later "
"on."
msgstr ""

#: ../system/subscription.rst:222
msgid "Receipt"
msgstr ""

#: ../system/subscription.rst:221
msgid ""
"Use the arrow to download the invoice in question. You can download all "
"available invoices any time you need to here!"
msgstr ""

#: ../system/subscription.rst:None
msgid "Screenshot showing payment history of a hosted instance"
msgstr ""

#: ../system/subscription.rst:229
msgid "FAQ"
msgstr ""

#: ../system/subscription.rst:233
msgid "I set up a trial account but am missing functions to test"
msgstr ""

#: ../system/subscription.rst:232
msgid ""
"The trial instance is running within the professional package allowing up to "
"three agents."
msgstr ""

#: ../system/subscription.rst:236
msgid "Can I change package within the trial?"
msgstr ""

#: ../system/subscription.rst:236
msgid "No. As soon as the package is changed the subscription begins."
msgstr ""

#: ../system/subscription.rst:241
msgid "What happens to my trial instance after the trial period ended?"
msgstr ""

#: ../system/subscription.rst:239
msgid ""
"Your instance will automatically be canceled for you. Please see *What "
"happens to my instance after it has been canceled?* for more."
msgstr ""

#: ../system/subscription.rst:254
msgid "What happens to my instance after it has been canceled?"
msgstr ""

#: ../system/subscription.rst:244
msgid "That depends slightly on your instance state:"
msgstr ""

#: ../system/subscription.rst:250
msgid "Trial instance"
msgstr ""

#: ../system/subscription.rst:247
msgid ""
"If you're still on trial, we will ice your instance and remind you once "
"again about your instance. We then will wait some days and remove your "
"instance from our system. This is the last time we will inform you by Email."
msgstr ""

#: ../system/subscription.rst:254
msgid "Paid instance"
msgstr ""

#: ../system/subscription.rst:253
msgid ""
"If you're a paying customer and canceled your subscription, the instance "
"removal will take place the day after your last subscription day."
msgstr ""

#: ../system/subscription.rst:256
msgid "Can removed instances be restored?"
msgstr ""

#: ../system/subscription.rst:257
msgid "No. Once your instance has been removed, a restoration is not possible."
msgstr ""

#: ../system/system-report.rst:2
msgid "System Report"
msgstr ""

#: ../system/system-report.rst:4
msgid ""
"In this place you can't configure Zammad. Instead you can obtain a system "
"report about Zammad and its configuration."
msgstr ""

#: ../system/system-report.rst:7
msgid ""
"See the description in Zammad for an explanation. You can even find a "
"preview of the included data below the **Download** button."
msgstr ""

#: ../system/system-report.rst:10
msgid ""
"Zammad never sends this automatically to anyone. It is a manual process only "
"to provide better support based on your configuration."
msgstr ""

#: ../system/translations.rst:2
msgid "Translations"
msgstr ""

#: ../system/translations.rst:4
msgid ""
"Translations of Zammad are processed centrally in our `Weblate instance "
"<https://translations.zammad.org/>`_. This allows non-developers to review "
"and update translation texts of the language they actually speak."
msgstr ""

#: ../system/translations.rst:9
msgid ""
"Your language is in an incomplete translation state or has typos? Please "
"consider helping us in sorting this out! All you need is either a GitHub "
"account or to register directly in our instance."
msgstr ""

#: ../system/translations.rst:13
msgid ""
"Did you know? This is also where the documentation translations are handled. "
"🤓"
msgstr ""

#: ../system/translations.rst:15
msgid ""
"Have a look in our :docs:`contribution section </contributing/start."
"html#translation>` in the system documentation to get started!"
msgstr ""

#: ../system/translations.rst:20
msgid "Local Translations"
msgstr ""

#: ../system/translations.rst:22
msgid ""
"Apart from these system translations, there's still local translations you "
"can manage. This is relevant if you added custom objects that require "
"translations or even custom states and priorities."
msgstr ""

#: ../system/translations.rst:None
msgid "Translation management screen within the admin menu"
msgstr ""

#: ../system/translations.rst:31
msgid "Updating Translations"
msgstr ""

#: ../system/translations.rst:33
msgid ""
"Because of how Zammad ships translations, the only way to update the system "
"translations is to update your Zammad installation. The benefit of this is "
"that you no longer need internet access during a Zammad upgrade as the "
"package has everything it requires already."
msgstr ""

#: ../system/translations.rst:39
msgid "Translation of Custom Objects"
msgstr ""

#: ../system/translations.rst:41
msgid ""
"No problem at all! You can customize any translation locally, even if it is "
"not initially provided by the system."
msgstr ""

#: ../system/translations.rst:44
msgid ""
"Translation is supported for a broad number of features, including but not "
"limited to custom:"
msgstr ""

#: ../system/translations.rst:47
msgid "Object Attributes"
msgstr ""

#: ../system/translations.rst:48
msgid "Ticket Macros"
msgstr ""

#: ../system/translations.rst:49
msgid "Ticket Overviews"
msgstr ""

#: ../system/translations.rst:50
msgid "Ticket Priorities"
msgstr ""

#: ../system/translations.rst:51
msgid "Ticket States"
msgstr ""

#: ../system/translations.rst:54
msgid "Customizing Translations"
msgstr ""

#: ../system/translations.rst:56
msgid ""
"Within the translation screen, simply click on the **New Translation** "
"button."
msgstr ""

#: ../system/translations.rst:None
msgid "New translation dialog"
msgstr ""

#: ../system/translations.rst:62
msgid ""
"In the dialog you can immediately enter the exact translation source (if you "
"know it) and your custom translation text for it and click **Submit**."
msgstr ""

#: ../system/translations.rst:65
msgid ""
"Alternatively, try to search for translation suggestions in the list below. "
"Selecting an item from the list will pre-fill the translation source for you "
"and then you can just enter your custom translation."
msgstr ""

#: ../system/translations.rst:69
msgid ""
"The target language will always default to your current language selection. "
"If you need to translate for a different language, simply change the "
"selection before submitting."
msgstr ""

#: ../system/translations.rst:73
msgid ""
"All your custom translations will show up in the overview table when added. "
"And they will even persist across Zammad updates!"
msgstr ""

#: ../system/translations.rst:76
msgid ""
"Make sure to reload your browser if a translated string is not displayed."
msgstr ""

#: ../system/translations.rst:80
msgid "Reverting to Original Translations"
msgstr ""

#: ../system/translations.rst:82
msgid ""
"If you want to revert a custom translation to original text, simply use the "
"appropriate action within the row of the overview table."
msgstr ""

#: ../system/translations.rst:85
msgid ""
"Depending on the type of the translation source, the action has a slightly "
"different name:"
msgstr ""

#: ../system/translations.rst:88
msgid "**Reset** for customized system translations"
msgstr ""

#: ../system/translations.rst:89
msgid "**Remove** for customized local translations"
msgstr ""

#: ../system/translations.rst:91
msgid ""
"In both cases, the action will remove the customized translation after a "
"confirmation."
msgstr ""

#: ../system/translations.rst:None
msgid "Screenshot showing the location of the Remove action"
msgstr ""

#: ../system/translations.rst:99
msgid "Inline Translations"
msgstr ""

#: ../system/translations.rst:101
msgid ""
"If you prefer a more hands-on approach, you can activate the inline or on-"
"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any "
"time and on any screen."
msgstr ""

#: ../system/translations.rst:105
msgid ""
"All customizable translation texts will be highlighted for you on the "
"screen. Just click into the highlighted area and update the text in place."
msgstr ""

#: ../system/translations.rst:None
msgid "Inline translation mode activated for the Overview screen"
msgstr ""

#: ../system/translations.rst:112
msgid ""
"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to "
"deactivate."
msgstr ""

#: ../system/translations.rst:117
msgid ""
"Even though it's available on any screen, the inline translation feature "
"requires admin permissions. It works only for the current language "
"selection. If you need to translate a different language, first change the "
"language in your :user-docs:`profile settings </extras/profile-and-settings."
"html>`."
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 ""