diff --git a/channels/form.rst b/channels/form.rst index 5b0e679e..7c55609e 100644 --- a/channels/form.rst +++ b/channels/form.rst @@ -3,7 +3,7 @@ Forms 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 +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. .. figure:: /images/channels/form/form-channel-management.png @@ -62,19 +62,19 @@ need to copy to your website. So let's talk about the options the designer provides. -:Title of the form: +Title of the form 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. Default: ``Feedback Form`` -:Name of form submit button: +Name of form submit button 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. -:Message after sending form: +Message after sending form After your user pressed the submit button, they will be provided with a message containing the ticket number of the newly created ticket. @@ -85,7 +85,7 @@ So let's talk about the options the designer provides. Thank you for your inquiry (#31015)! We'll contact you as soon as possible. -:Options: +Options Zammad provides the following additional configuration options for your form. Enable debugging for implementation @@ -168,7 +168,7 @@ Requirements 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. -:Header section: +Header section The first code block provides you with Zammad's current jQuery dependency. This script section usually belongs to your website's header section. @@ -185,7 +185,7 @@ apply Zammad's web form to your website. It basically consists of two parts. Do not mix jQuery versions - it's likely to break something. -:Body section: +Body section The second code block is the actual code required for your form to run. The first line containing ``id="zammad-feedback-form"`` highly depends on diff --git a/locale/admin-docs.pot b/locale/admin-docs.pot index f0866a93..4a7438f6 100644 --- a/locale/admin-docs.pot +++ b/locale/admin-docs.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad Admin Documentation pre-release\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -486,7 +486,7 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:156 #: ../channels/email/accounts/account-setup.rst:281 -#: ../manage/webhook/add.rst:72 +#: ../manage/webhook/add.rst:74 #: ../settings/security/third-party/saml.rst:170 #: ../system/integrations/i-doit.rst:77 msgid "SSL verification" @@ -504,6 +504,7 @@ msgstr "" #: ../includes/ssl-verification-warning.rst:4 #: ../includes/ssl-verification-warning.rst:4 #: ../includes/ssl-verification-warning.rst:4 +#: ../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 "" @@ -1042,7 +1043,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 #: ../manage/scheduler.rst:91 -#: ../manage/webhook/add.rst:118 +#: ../manage/webhook/add.rst:120 #: ../system/integrations/cti/includes/inbound-calls.include.rst:10 #: ../system/integrations/cti/includes/outbound-calls.include.rst:20 #: ../system/integrations/cti/includes/inbound-calls.include.rst:9 @@ -2607,7 +2608,7 @@ msgid "Forms" msgstr "" #: ../channels/form.rst:4 -msgid "Feedback or contact forms are used on websites quite often. Usually they will generate an email which will be sent to somebody who forwards it and so on. With Zammad it’s quite easy to integrate these forms into your website and directly generate tickets with them. In just 2 minutes." +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 @@ -2674,7 +2675,7 @@ msgstr "" #: ../manage/overviews.rst:0 #: ../manage/scheduler.rst:94 #: ../manage/templates.rst:43 -#: ../manage/webhook/add.rst:127 +#: ../manage/webhook/add.rst:129 #: ../system/integrations/i-doit.rst:43 msgid "Active" msgstr "" @@ -2716,7 +2717,7 @@ msgstr "" msgid "So let's talk about the options the designer provides." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:70 msgid "Title of the form" msgstr "" @@ -2728,7 +2729,7 @@ msgstr "" msgid "Default: ``Feedback Form``" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:75 msgid "Name of form submit button" msgstr "" @@ -2736,7 +2737,7 @@ msgstr "" msgid "If Zammad's default display name of the submit button does not fit, you can provide your own wording with this option. It will be used every time the form is shown." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:86 msgid "Message after sending form" msgstr "" @@ -2748,7 +2749,7 @@ msgstr "" msgid "Default *after* sending a form will look like so:" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:146 msgid "Options" msgstr "" @@ -2884,7 +2885,7 @@ msgstr "" msgid "The requirement section provides you with everything you need in order to apply Zammad's web form to your website. It basically consists of two parts." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:186 msgid "Header section" msgstr "" @@ -2900,7 +2901,7 @@ msgstr "" msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:207 msgid "Body section" msgstr "" @@ -4815,11 +4816,11 @@ 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." +msgid "Determine a name, a time-zone, the business hours to be used for this calendar and special holidays. In addition, you can subscribe to the iCalendar, which will automatically load all holidays from Google (updated once a day) ... and you can add a note." msgstr "" #: ../manage/groups/access-levels.rst:2 -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5147,7 +5148,7 @@ msgid "This setting allows you to decide if, upon a reopen of a ticket, the last msgstr "" #: ../manage/groups/settings.rst:62 -msgid "The ticket will remain to the last agent who owned it. This is the default value" +msgid "The ticket will remain with the last agent who owned it. This is the default value." msgstr "" #: ../manage/groups/settings.rst:65 @@ -5549,7 +5550,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -5581,14 +5582,11 @@ 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" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -5599,7 +5597,7 @@ msgstr "" msgid "There are also a few other settings that affect who can use a macro or how it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -5613,75 +5611,72 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "Unlike triggers, the scheduler, and text modules, macro actions do **not** support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 -msgid "If the ticket is missing a required attribute and the macro doesn’t set it, then **no actions will be applied**." +#: ../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:36 -msgid "After running this macro, should Zammad remain on the current tab, close it, or automatically switch to the next ticket? (Does not apply when running macros “in bulk”.)" +#: ../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:41 -msgid "What should other Zammad admins know about this macro? (Visible only via the “Edit: Macro” dialog, Rails console, and API.)" +#: ../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:45 +#: ../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:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../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:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "You can delete or even clone existing macros in the Admin Panel under **Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 -msgid "When cloning a macro, you *must* click “Submit” for the duplicate to be created." +#: ../manage/macros/how-do-they-work.rst:61 +msgid "When cloning a macro, you *must* click \"Submit\" for the duplicate to be created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -5689,7 +5684,7 @@ msgid "To get you up and running quickly, here are some examples of the kinds of msgstr "" #: ../manage/macros/learn-by-example.rst:9 -msgid "If they don't make sense to you, don't worry—just skip ahead to :doc:`/manage/macros/how-do-they-work` to learn about all the options in detail, then come back here to see them in action." +msgid "If they don't make sense to you, don't worry - just skip ahead to :doc:`/manage/macros/how-do-they-work` to learn about all the options in detail, then come back here to see them in action." msgstr "" #: ../manage/macros/learn-by-example.rst:14 @@ -5726,11 +5721,11 @@ msgid "💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean u msgstr "" #: ../manage/macros/learn-by-example.rst:29 -msgid "If you want to set a ticket’s state to *pending reminder*, it’s usually a two-step process—first select the state, then select a date. To always set a reminder for the same, fixed amount of time (say, seven days later), you can bundle the whole change into a macro:" +msgid "If you want to set a ticket's state to *pending reminder*, it's usually a two-step process - first select the state, then select a date. To always set a reminder for the same, fixed amount of time (say, seven days later), you can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -5749,15 +5744,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -5766,99 +5761,100 @@ msgid "Organizations" msgstr "" #: ../manage/organizations/index.rst:4 -msgid "Depending on your organization’s IT capabilities, organizations can be managed individually or in bulk." +msgid "Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 -#: ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 +#: ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "Organizations currently cannot be removed. The only exception is Zammad's :doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "Unlike users, agents cannot just create new organizations. Check the :doc:`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "Because of how organization references work with users, external syncs like LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "Organizations with many members can cause a fairly high system load in some situations. This especially affects organizations whose members run many updates, for example ticket creations or frequent communication. A lot of linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 -msgid "Most of the attributes you can set on organizations are self-explanatory. The ones that aren’t are described below." +#: ../manage/organizations/index.rst:50 +msgid "Most of the attributes you can set on organizations are self-explanatory. The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 +#: ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 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:72 +#: ../manage/organizations/index.rst:71 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:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 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:86 +#: ../manage/organizations/index.rst:85 msgid "Sharing organizations don't just affect customers, however, if you want to provide ticket access to agents, please see the :ref:`permission-guide`." msgstr "" @@ -5867,92 +5863,92 @@ msgid "Screenshot showing \"My Organization Tickets\" overview with tickets\n" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 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:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "Domain based assignment only works for *newly created* users and has no effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 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:117 +#: ../manage/organizations/index.rst:116 msgid "At the time Zammad allows *one* domain per organization. You may also want to ensure to not use free mailer domains like ``gmail.com`` for these assignments." msgstr "" -#: ../manage/organizations/index.rst:132 -#: ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 +#: ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 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" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 -#: ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 +#: ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 -#: ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 +#: ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 -msgid "😵 **Are you using the Note field to keep track of your own “custom” organization attributes?**" +#: ../manage/organizations/index.rst:136 +msgid "😵 **Are you using the Note field to keep track of your own \"custom\" organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 -#: ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 +#: ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 -#: ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 +#: ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 -msgid "Disabling this flag is a soft alternative to deleting an organization. So what’s the difference?" +#: ../manage/organizations/index.rst:144 +msgid "Disabling this flag is a soft alternative to deleting an organization. So what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "There is no way to restore a deleted organization; inactive organizations can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -5960,8 +5956,8 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 -msgid "A slashed-out 🏢 icon indicates an inactive organization. In other cases, inactive organizations are greyed out." +#: ../manage/organizations/index.rst:156 +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 @@ -6328,7 +6324,7 @@ msgid "Screenshot showing the public links management interface within\n" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -7261,7 +7257,7 @@ msgid "To make it work, you need two separate roles: one with ``ticket.agent`` a msgstr "" #: ../manage/roles/index.rst:2 -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -7278,15 +7274,15 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 -msgid "Why would you want this? Agents get :doc:`overviews ` of all the tickets they're *assigned to* (among other things), while customers get an overview of all the tickets they've *opened*. But some teams use Zammad for both internal and public communication, so their agents need both." +msgid "Why would you want this? Agents get :doc:`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:25 -msgid "Having both roles also changes what you see in the ticket view, depending on whether you're the “customer” or not." +msgid "Having both roles also changes what you see in the ticket view, depending on whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -7294,7 +7290,7 @@ msgid "💡 **LDAP/Active Directory users:**" msgstr "" #: ../manage/roles/index.rst:30 -msgid "Syncing your LDAP “groups” to Zammad roles can make access management *way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." +msgid "Syncing your LDAP \"groups\" to Zammad roles can make access management *way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -7338,11 +7334,11 @@ msgid "create/edit knowledge base articles" msgstr "" #: ../manage/roles/index.rst:61 -msgid "Zammad has dozens of these permissions, which is a lot to keep track of. So instead of saying “This user has permissions A, B, and C”, Zammad says “The *agent role* has permissions A, B, and C, and this user is an agent.”" +msgid "Zammad has dozens of these permissions, which is a lot to keep track of. So instead of saying \"This user has permissions A, B, and C\", Zammad says \"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 -msgid "This makes creating user accounts for new agents a whole lot simpler, and it also makes it easier to invent a new permission D and say “All existing agents can do *that* now, too.”" +msgid "This makes creating user accounts for new agents a whole lot simpler, and it also makes it easier to invent a new permission D and say \"All existing agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -7732,6 +7728,10 @@ msgstr "" 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 "" @@ -7989,12 +7989,16 @@ msgstr "" 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." +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 @@ -8021,7 +8025,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -8799,8 +8803,12 @@ msgstr "" 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: **activators**, **conditions** and **changes**. Activator defines “when the question is asked?”. Conditions answer the question, “when should this trigger fire?” Changes answer the question, “what should happen when it does?”" +msgid "Triggers consist of three parts: **activators**, **conditions** and **changes**. Activator defines \"when the question is asked?\". Conditions answer the question, \"when should this trigger fire?\" Changes answer the question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -8852,7 +8860,7 @@ msgid "An always action trigger which is listening on the priority **1 low** wil msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 -msgid "**Time event** activator simply checks if **Conditions** match. This is the same behavior as Action-based activator's „Always“ mode." +msgid "**Time event** activator simply checks if **Conditions** match. This is the same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -8936,12 +8944,16 @@ msgstr "" msgid "Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst: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 "If they don't make sense to you, don't worry—just skip ahead to :doc:`/manage/trigger/how-do-they-work` to learn about all the options in detail, then come back here to see them in action." +msgid "If they don't make sense to you, don't worry - just skip ahead to :doc:`/manage/trigger/how-do-they-work` to learn about all the options in detail, then come back here to see them in action." msgstr "" #: ../manage/trigger/learn-by-example.rst:12 @@ -8949,7 +8961,7 @@ 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:" +msgid "Emma Taylor is responsible for all sales internally, so if a new ticket has the word \"order\" in the subject, assign it to her and make sure it's set with a high priority:" msgstr "" #: ../manage/trigger/learn-by-example.rst:22 @@ -8961,7 +8973,7 @@ msgid "📨 **Not all automated messages come from triggers!**" msgstr "" #: ../manage/trigger/learn-by-example.rst:28 -msgid "For instance, when *agents* receive a system email about a newly created ticket, that’s built into the system itself. If you need to customize those, you will have to :doc:`manually edit files on your server `." +msgid "For instance, when *agents* receive a system email about a newly created ticket, that's built into the system itself. If you need to customize those, you will have to :doc:`manually edit files on your server `." msgstr "" #: ../manage/trigger/limitations.rst:4 @@ -9065,86 +9077,82 @@ msgid "Users" msgstr "" #: ../manage/users/index.rst:4 -msgid "Depending on your organization's IT capabilities, users can be managed individually or in bulk, or even synchronized with third-party directory services." +msgid "Users can be managed individually via UI, via API or even synchronized with third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 -msgid "How? Zammad checks the sender of every incoming message at every inbox it monitors, and if it doesn't recognize the address, ✨ **poof**—new customer account!" +#: ../manage/users/index.rst:35 +msgid "How? Zammad checks the sender of every incoming message at every inbox it monitors, and if it doesn't recognize the address, ✨ **poof** - new customer account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "(Your customers never need to set a password. Of course, they can if they want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "Most of the attributes you can set on user accounts are self-explanatory. The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar ` or the :user-docs:`ticket pane `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "A user's email and login may differ, but **either one can be used to sign in.**" msgstr "" @@ -9152,67 +9160,67 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 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:81 +#: ../manage/users/index.rst:80 msgid "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "Yes, administrators really do have the power to change other users' passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 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:96 +#: ../manage/users/index.rst:95 msgid "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "This option allows you to assign more organizations, in addition to the user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 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:110 +#: ../manage/users/index.rst:109 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:115 +#: ../manage/users/index.rst:114 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:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 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 "" @@ -9220,31 +9228,31 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 -msgid "😵 **Are you using the Note field to keep track of your own “custom” user attributes?**" +#: ../manage/users/index.rst:135 +msgid "😵 **Are you using the Note field to keep track of your own \"custom\" user attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "Disabling this flag is a soft alternative to deleting a user. So what's the difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "There is no way to restore a deleted user; inactive users can be reactivated at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 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:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -9252,15 +9260,15 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 -msgid "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive users are greyed out." +#: ../manage/users/index.rst:158 +msgid "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 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:170 +#: ../manage/users/index.rst:169 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." msgstr "" @@ -9268,15 +9276,15 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "**Top:** User's roles decide what kind of actions they can perform and which :doc:`groups ` they belong to. **Bottom:** Group assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "The group access table is only visible in **agent profiles**, when there is **more than one active group** in the system." msgstr "" @@ -9445,14 +9453,11 @@ msgid "Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/sched msgstr "" #: ../manage/webhook.rst:20 -#: ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +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." +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 @@ -9472,7 +9477,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -9504,7 +9509,7 @@ msgid "Webhooks are defined globally. This allows you to use one specific endpoi msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -9599,32 +9604,32 @@ msgstr "" msgid "Defaults to ``yes`` - if you're using unsecure self signed certificates set this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 +#: ../manage/webhook/add.rst:80 msgid "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 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 +#: ../manage/webhook/add.rst:89 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 "" @@ -9632,15 +9637,15 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "Defaults to off - webhook will always send :ref:`webhook-payload-default` to the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "When switched on, a code editor will be shown below, where you can configure custom payload for your webhook in JSON format. To insert supported :doc:`/system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" @@ -9648,23 +9653,23 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "Custom payload must be valid JSON syntax! Code editor will inform you via automated hints if there is an issue with the code. Also, it will not be possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "Pre-defined webhooks will always provide an initial custom payload, specific for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "If required you can leave useful information for other Zammad admins to understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "If set to ``inactive`` you can no longer select the webhook within trigger or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 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 "" @@ -13957,6 +13962,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" 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 "" @@ -14274,6 +14283,10 @@ msgstr "" 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 "" @@ -14760,6 +14773,12 @@ msgstr "" 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 +#: ../system/integrations/checkmk/index.rst:16 +#: ../system/integrations/checkmk/index.rst:16 +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 "" diff --git a/manage/calendars.rst b/manage/calendars.rst index e561cb81..02eb53b4 100644 --- a/manage/calendars.rst +++ b/manage/calendars.rst @@ -37,7 +37,7 @@ Edit .. figure:: /images/manage/calendars/editting-calendars.png ---> determine a name, a time-zone, the business hours to be used for this +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. diff --git a/manage/groups/settings.rst b/manage/groups/settings.rst index 961eee62..588be890 100644 --- a/manage/groups/settings.rst +++ b/manage/groups/settings.rst @@ -59,8 +59,8 @@ Assign follow-ups nobody. yes - The ticket will remain to the last agent who owned it. - This is the default value + The ticket will remain with the last agent who owned it. + This is the default value. no The owner assignment of the ticket will be removed. diff --git a/manage/macros.rst b/manage/macros.rst index 5b1a41fc..de4a69ac 100644 --- a/manage/macros.rst +++ b/manage/macros.rst @@ -1,7 +1,7 @@ Macros ====== -Macros are **🖱️ one-click shortcuts** for applying changes to a ticket. +Macros are **🖱️ one-click actions** for applying changes to a ticket. If you find yourself making the same changes to lots of tickets (*e.g.,* close-and-tag-as-spam or reassign-to-another-group), @@ -31,7 +31,7 @@ You can create or edit macros on the Macros page of the admin panel: .. figure:: /images/manage/macros/macro-overview.png :align: center :width: 80% - :alt: Screenshot of “Macros” page in admin panel + :alt: Screenshot of "Macros" page in admin panel .. toctree:: :maxdepth: 1 diff --git a/manage/macros/how-do-they-work.rst b/manage/macros/how-do-they-work.rst index 90401d4e..0c296fb1 100644 --- a/manage/macros/how-do-they-work.rst +++ b/manage/macros/how-do-they-work.rst @@ -1,10 +1,11 @@ -How do they work? -================= +How do macros work +================== Macros are made up of **actions** (changes to a ticket). You can add as many actions to a macro as you want. -There are also a few other settings that affect who can use a macro or how it behaves. +There are also a few other settings that affect who can use a macro or how it +behaves. Creating Macros --------------- @@ -29,23 +30,23 @@ Creating Macros :doc:`/system/variables`. .. warning:: If the ticket is missing a required attribute - and the macro doesn’t set it, then **no actions will be + and the macro doesn't set it, then **no actions will be applied**. :Once completed...: 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”.) + (Does not apply when running macros "in bulk".) :Note: What should other Zammad admins know about this macro? - (Visible only via the “Edit: Macro” dialog, Rails console, and API.) + (Visible only via the "Edit: Macro" dialog, Rails console, and API.) :Groups: Which :doc:`/manage/groups/index` are allowed to see/use this macro? :Active: - Choose “inactive” to disable this macro without deleting it. + Choose "inactive" to disable this macro without deleting it. Managing Macros --------------- @@ -57,5 +58,5 @@ You can delete or even clone existing macros in the Admin Panel under **Manage > :width: 80% :alt: Screencast showing the creation of a new macro via cloning and its removal - When cloning a macro, you *must* click “Submit” for the duplicate + When cloning a macro, you *must* click "Submit" for the duplicate to be created. diff --git a/manage/macros/learn-by-example.rst b/manage/macros/learn-by-example.rst index 8130f505..7f6888e8 100644 --- a/manage/macros/learn-by-example.rst +++ b/manage/macros/learn-by-example.rst @@ -1,12 +1,12 @@ -Learn by example -================ +Macro Example +============= To get you up and running quickly, here are some examples of the kinds of one-click actions you can set up using macros. -.. hint:: +.. hint:: - If they don't make sense to you, don't worry—just skip ahead to + If they don't make sense to you, don't worry - just skip ahead to :doc:`/manage/macros/how-do-they-work` to learn about all the options in detail, then come back here to see them in action. @@ -23,15 +23,15 @@ of the kinds of one-click actions you can set up using macros. :width: 70% :alt: Screencast showing spam macro configuration and behavior - .. tip:: 💡 Run this macro in a :doc:`/manage/scheduler` + .. tip:: 💡 Run this macro in a :doc:`/manage/scheduler` to periodically clean up unwanted tickets. -2. 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. +2. 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: - :Note: “Postponing ticket for 7 days.” (🔒 internal visibility only) + :Note: "Postponing ticket for 7 days." (🔒 internal visibility only) :State: pending reminder :Pending Till: relative / 7 / days :Owner: current user diff --git a/manage/organizations/index.rst b/manage/organizations/index.rst index 2d2ed103..b53f4202 100644 --- a/manage/organizations/index.rst +++ b/manage/organizations/index.rst @@ -1,8 +1,7 @@ Organizations ============= -Depending on your organization’s IT capabilities, -organizations can be managed individually or in bulk. +Organizations can be managed individually via UI, via CSV import or the API. .. figure:: /images/manage/organizations/general-view-of-a-busy-organization.png :alt: Creating and editing users directly in the Admin Panel @@ -49,7 +48,7 @@ Reference Guide: Organization Details ------------------------------------- Most of the attributes you can set on organizations are self-explanatory. -The ones that aren’t are described below. +The ones that aren't are described below. .. figure:: /images/manage/organizations/administrative-changing-organization-settings.png :alt: The edit organization dialog, showing the various organization detail fields @@ -58,7 +57,7 @@ The ones that aren’t are described below. User details can be set in the **New/Edit Organization** dialog. -.. note:: 🕵️ **Admins aren’t the only ones who can change these settings.** +.. note:: 🕵️ **Admins aren't the only ones who can change these settings.** In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail @@ -105,7 +104,7 @@ The ones that aren’t are described below. .. note:: Domain based assignment only works for *newly created* users and has no - effect on existing users. + effect on existing users. 🌐 Domain Add the email domain of the organization with this option. It's being used @@ -125,7 +124,7 @@ The ones that aren’t are described below. and :doc:`/manage/overviews` just for VIPs. .. figure:: /images/manage/organizations/vip-org-in-a-ticket.png - :alt: Ticket view showing a VIP organization’s avatar with a crown on it + :alt: Ticket view showing a VIP organization's avatar with a crown on it :align: center :width: 90% @@ -135,19 +134,19 @@ The ones that aren’t are described below. Notes are visible to all staff members, **including agents**. .. hint:: 😵 **Are you using the Note field - to keep track of your own “custom” organization attributes?** + to keep track of your own "custom" organization attributes?** - Wish you could add your own fields to the New/Edit Organization dialog? + Wish you could add your own fields Organizations? You can! To learn more, see :doc:`/system/objects`. ▶️ Active Disabling this flag is a soft alternative to deleting an organization. - So what’s the difference? + So what's the difference? 1. There is no way to restore a deleted organization; inactive organizations can be reactivated at any time. - + 2. Inactive organizations still appear in search results: .. figure:: /images/manage/organizations/search-results-showing-organizations.png @@ -155,4 +154,4 @@ The ones that aren’t are described below. :align: center A slashed-out 🏢 icon indicates an inactive organization. - In other cases, inactive organizations are greyed out. + In other cases, inactive organizations are grayed out. diff --git a/manage/public-links.rst b/manage/public-links.rst index e18ac8e3..535c0d53 100644 --- a/manage/public-links.rst +++ b/manage/public-links.rst @@ -10,7 +10,7 @@ useful links to other services if needed. :alt: Screenshot showing the public links management interface within the settings -Learn how to ... +See here: * :ref:`public_links_add_new` * :ref:`public_links_manage_existing` diff --git a/manage/roles/index.rst b/manage/roles/index.rst index cbc859b0..bd51ace9 100644 --- a/manage/roles/index.rst +++ b/manage/roles/index.rst @@ -13,21 +13,21 @@ of its powerful, flexible, and fine-grained permission system. Assign user privileges in the Admin Panel, under **Manage > Roles**. -.. note:: 👀 Users can have both “agent” and “customer” roles at the same time! +.. note:: Users can have both "agent" and "customer" roles at the same time! Why would you want this? Agents get :doc:`overviews ` - of all the tickets they're *assigned to* (among other things), + 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. Having both roles also changes what you see in the ticket view, - depending on whether you're the “customer” or not. + depending on whether you're the "customer" or not. .. tip:: 💡 **LDAP/Active Directory users:** - Syncing your LDAP “groups” to Zammad roles + Syncing your LDAP "groups" to Zammad roles can make access management *way* easier. To learn more, see :doc:`/system/integrations/ldap/index`. @@ -60,13 +60,13 @@ users might want to do throughout the system, such as: Zammad has dozens of these permissions, which is a lot to keep track of. -So instead of saying “This user has permissions A, B, and C”, -Zammad says “The *agent role* has permissions A, B, and C, -and this user is an agent.” +So instead of saying "This user has permissions A, B, and C", +Zammad says "The *agent role* has permissions A, B, and C, +and this user is an agent." This makes creating user accounts for new agents a whole lot simpler, and it also makes it easier to invent a new permission D -and say “All existing agents can do *that* now, too.” +and say "All existing agents can do *that* now, too." 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, diff --git a/manage/slas/how-do-they-work.rst b/manage/slas/how-do-they-work.rst index 2b410cf1..c8b2d4a4 100644 --- a/manage/slas/how-do-they-work.rst +++ b/manage/slas/how-do-they-work.rst @@ -1,5 +1,5 @@ -How do they work? ------------------ +How do SLAs work +---------------- You can define several independent SLAs, however, ensure to have no overlapping SLAs as their calculations may not work as you intended them originally. diff --git a/manage/slas/learn-by-example.rst b/manage/slas/learn-by-example.rst index 21d309c0..c22a1c8d 100644 --- a/manage/slas/learn-by-example.rst +++ b/manage/slas/learn-by-example.rst @@ -1,5 +1,5 @@ -Learn by example ----------------- +SLA example +----------- 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 @@ -7,7 +7,7 @@ your standard! .. hint:: - If they don’t make sense to you, don’t worry—just skip ahead to + 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. @@ -18,7 +18,7 @@ them in all samples. * Sales * Support * 2nd Level - * **Attribtues** + * **Attributes** * User / VIP (default, Boolean) * Organization / Support-Contract (Single selection field, ``None`` as default value) diff --git a/manage/trigger/how-do-they-work.rst b/manage/trigger/how-do-they-work.rst index 6eddaeed..9a607a33 100644 --- a/manage/trigger/how-do-they-work.rst +++ b/manage/trigger/how-do-they-work.rst @@ -1,10 +1,10 @@ -How do they work? -================= +How do trigger work +=================== Triggers consist of three parts: **activators**, **conditions** and **changes**. -Activator defines “when the question is asked?”. Conditions answer the question, -“when should this trigger fire?” Changes answer the question, -“what should happen when it does?” +Activator defines "when the question is asked?". Conditions answer the question, +"when should this trigger fire?" Changes answer the question, +"what should happen when it does?" Triggers are evaluated in alphabetical order, by **name.** In some situations triggers might be the wrong choice, see @@ -45,7 +45,7 @@ Triggers support two types of activators: set **1 low**. **Time event** activator simply checks if **Conditions** match. -This is the same behavior as Action-based activator's „Always“ mode. +This is the same behavior as Action-based activator's „Always" mode. When creating a trigger, choose activator here: diff --git a/manage/trigger/learn-by-example.rst b/manage/trigger/learn-by-example.rst index 729bf7d3..abe629fe 100644 --- a/manage/trigger/learn-by-example.rst +++ b/manage/trigger/learn-by-example.rst @@ -1,10 +1,10 @@ -Learn by example +Trigger examples ================ To get you up and running quickly, here are some examples of the kinds of automation tasks you can set up with triggers. -.. hint:: If they don't make sense to you, don't worry—just skip ahead to +.. hint:: If they don't make sense to you, don't worry - just skip ahead to :doc:`/manage/trigger/how-do-they-work` to learn about all the options in detail, then come back here to see them in action. @@ -14,7 +14,7 @@ of the kinds of automation tasks you can set up with triggers. .. figure:: /images/manage/trigger/move-tickets-of-specific-customer-to-specific-group.png 2. 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 + the word "order" in the subject, assign it to her and make sure it's set with a high priority: .. figure:: /images/manage/trigger/trigger-based-prioritize-change.png @@ -27,7 +27,7 @@ of the kinds of automation tasks you can set up with triggers. For instance, when *agents* receive a system email about a newly created ticket, - that’s built into the system itself. + that's built into the system itself. If you need to customize those, you will have to :doc:`manually edit files on your server `. diff --git a/manage/users/index.rst b/manage/users/index.rst index abd7509e..06d89106 100644 --- a/manage/users/index.rst +++ b/manage/users/index.rst @@ -1,9 +1,8 @@ Users ===== -Depending on your organization's IT capabilities, -users can be managed individually or in bulk, -or even synchronized with third-party directory services. +Users can be managed individually via UI, via API or even synchronized with +third-party directory services. .. figure:: /images/manage/users/managing-users-manually.png :alt: Creating and editing users directly in the Admin Panel @@ -36,7 +35,7 @@ Learn more about managing users... How? Zammad checks the sender of every incoming message at every inbox it monitors, and if it doesn't recognize the address, - ✨ **poof**—new customer account! + ✨ **poof** - new customer account! (Your customers never need to set a password. Of course, they can if they want to, @@ -134,7 +133,7 @@ The ones that aren't are described below. Notes are visible to all staff members, **including agents**. .. hint:: 😵 **Are you using the Note field - to keep track of your own “custom” user attributes?** + to keep track of your own "custom" user attributes?** Wish you could add your own fields to the New/Edit User dialog? @@ -157,7 +156,7 @@ The ones that aren't are described below. :align: center A slashed-out 👤 icon indicates an inactive user. - In other cases, inactive users are greyed out. + In other cases, inactive users are grayed out. .. _user-details-group-access: diff --git a/manage/webhook.rst b/manage/webhook.rst index 1fdec17b..39abd171 100644 --- a/manage/webhook.rst +++ b/manage/webhook.rst @@ -16,11 +16,11 @@ poll the Zammad server every *n* minutes. Webhooks are available for :doc:`/manage/trigger` and :doc:`/manage/scheduler`. -How does it work? ------------------ +How do Webhooks work +-------------------- 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 +("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. @@ -31,7 +31,7 @@ following JSON data about new/updated tickets: * ticket attributes/metadata * *all* associated articles -* associated users (*e.g.* article senders, owners, etc.) +* associated users (e.g. article senders, owners, etc.) * associated user roles * associated user organizations (if applicable) * associated groups diff --git a/manage/webhook/add.rst b/manage/webhook/add.rst index 978a0892..aecfad83 100644 --- a/manage/webhook/add.rst +++ b/manage/webhook/add.rst @@ -4,7 +4,7 @@ Adding Webhooks Webhooks are defined globally. This allows you to use one specific endpoint for several triggers or schedulers. -.. warning:: **🦻 Default Zammad webhook payloads are specific** +.. warning:: **Default Zammad webhook payloads are specific** 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 @@ -71,6 +71,8 @@ You can configure the following information for webhooks: Defaults to ``yes`` - if you're using unsecure self signed certificates set this option to ``no``. + .. include:: /includes/ssl-verification-warning.rst + _`HTTP Basic Authentication Username` Set this if the endpoint requires HTTP basic authentication credentials.