Removed references to videos and placeholders

Author: ralf401

guides/additional-customization.rst

@@ -16,10 +16,10 @@ can select from pre-defined categories? No problem! You can even set it to
 required to have a proper base for statistics.
 
 Head over to the :doc:`object attributes page </system/objects>` where it is
-explained in detail or watch the video about how to create a mandatory category
-field for tickets.
+explained in detail.
 
-ADD VIDEO HERE (created).
+.. or watch the video about how to create a mandatory category field for tickets.
+.. ADD VIDEO HERE.
 
 Set Up Automation
 -----------------
@@ -37,14 +37,14 @@ dispatched to and what attributes you want to set for those tickets. You can
 find it in the :doc:`Filter </channels/email/filters>` tab in the email based
 channels.
 
-The following video shows three examples:
+.. The following video shows three examples:
 
-- An automatic deletion of old tickets and customers via scheduler
-- An email rule (postmaster filter) for a specific customer
-- A trigger to increase priority for tickets when a specific organization member
-  is involved.
+.. - An automatic deletion of old tickets and customers via scheduler
+.. - An email rule (postmaster filter) for a specific customer
+.. - A trigger to increase priority for tickets when a specific organization member
+..   is involved.
 
-ADD VIDEO HERE (created).
+.. ADD VIDEO HERE.
 
 Add Text Modules
 ----------------
@@ -58,10 +58,10 @@ or customer specific text like ticket title or customer name. Just type
 :kbd:`:` :kbd:`:` in the text module content editor to search for available
 variables.
 
-The video shows how to create a text module, including usage of variables and
-how it works for agents when dealing with a ticket.
+.. The video shows how to create a text module, including usage of variables and
+.. how it works for agents when dealing with a ticket.
 
-ADD VIDEO HERE (created).
+.. ADD VIDEO HERE.
 
 Enable Checklist Feature
 ------------------------
@@ -70,10 +70,10 @@ Zammad's :doc:`checklist feature </manage/checklist>` allows you to keep track
 of certain tasks in a ticket. The feature allows you to create checklist
 templates and link to other tickets as checklist item too.
 
-See how to set it up, create a template and reference to another ticket in a
-checklist item in the video.
+.. See how to set it up, create a template and reference to another ticket in a
+.. checklist item in the video.
 
-ADD VIDEO HERE (created).
+.. ADD VIDEO HERE.
 
 Add AI Agents
 -------------
@@ -86,12 +86,12 @@ configuration down:
 - Create an AI agent with the type of task you want to delegate
 - Call the AI agent in a trigger or scheduler job
 
-The video shows an example of how to set up an AI agent which rewrites the
-title of a ticket. A use case for this is when your customers often tend to use
-generic titles (like "problem") or you receive tickets from a web form which
-all have the same title.
+.. The video shows an example of how to set up an AI agent which rewrites the
+.. title of a ticket. A use case for this is when your customers often tend to use
+.. generic titles (like "problem") or you receive tickets from a web form which
+.. all have the same title.
 
-ADD VIDEO HERE (created).
+.. ADD VIDEO HERE (created).
 
 Next Steps
 ----------

guides/start-with-zammad.rst

@@ -51,12 +51,13 @@ Basic Setup
 Follow the steps below for a simple setup of Zammad. You can add some
 information via getting started wizard or skip the steps and configure it
 afterwards.
+
 The guide assumes your Zammad is not yet configured. In case you see the
 getting started wizard, provide as much information as you desire or skip it
-for a later configuration. The video below shows an example with providing
-minimal information in the wizard.
+for later configuration.
 
-ADD VIDEO HERE (created).
+.. The video below shows an example with providing minimal information in the wizard.
+.. ADD VIDEO HERE.
 
 Company Details
 ^^^^^^^^^^^^^^^
@@ -78,8 +79,8 @@ At this point, just add your groups and give them a fitting name. Create A
 structure in case you need it by setting parent groups. It is totally fine to
 stay with one group too, of course.
 
-You can find a video about a simple group and role configuration in the next
-section.
+.. You can find a video about a simple group and role configuration in the next
+.. section.
 
 Create or Modify Roles
 ^^^^^^^^^^^^^^^^^^^^^^
@@ -99,7 +100,7 @@ You can assign application and group permissions to a specific user as well. In
 case you expect more than one person with specific permissions, creating a role
 may be a good idea.
 
-ADD VIDEO HERE (created).
+.. ADD VIDEO HERE.
 
 Connect Email Accounts to Zammad
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -115,10 +116,10 @@ After adding an email channel, create one or more signatures. You can use one
 signature for many groups or create different signatures, depending on your
 company's department structure.
 
-The following video shows a dummy email channel configuration as well as adding
-email adresses and signatures to different groups.
+.. The following video shows a dummy email channel configuration as well as adding
+.. email adresses and signatures to different groups.
 
-VIDEO HERE (created).
+.. ADD VIDEO HERE.
 
 Configure Groups
 ^^^^^^^^^^^^^^^^
@@ -136,7 +137,7 @@ going to the first steps section and use the
 Make sure to assign the right role to each of the agents.
 This step sends out invitation emails to your agents.
 
-ADD VIDEO HERE (created).
+.. ADD VIDEO HERE.
 
 Further Steps
 -------------

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: 2025-11-24 09:43+0100\n"
+"POT-Creation-Date: 2025-11-26 07:37+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <[email protected]>\n"
@@ -5955,18 +5955,7 @@ msgid "Zammad allows you to easily add new fields for different objects like tic
 msgstr ""
 
 #: ../guides/additional-customization.rst:18
-msgid "Head over to the :doc:`object attributes page </system/objects>` where it is explained in detail or watch the video about how to create a mandatory category field for tickets."
-msgstr ""
-
-#: ../guides/additional-customization.rst:22
-#: ../guides/additional-customization.rst:47
-#: ../guides/additional-customization.rst:64
-#: ../guides/additional-customization.rst:76
-#: ../guides/additional-customization.rst:94
-#: ../guides/start-with-zammad.rst:59
-#: ../guides/start-with-zammad.rst:102
-#: ../guides/start-with-zammad.rst:139
-msgid "ADD VIDEO HERE (created)."
+msgid "Head over to the :doc:`object attributes page </system/objects>` where it is explained in detail."
 msgstr ""
 
 #: ../guides/additional-customization.rst:25
@@ -5981,22 +5970,6 @@ msgstr ""
 msgid "By default, there is already one active trigger which sends out auto-reply emails to customers after they contacted you in a new support case. You can even define in the channel configuration, to which group specific messages should be dispatched to and what attributes you want to set for those tickets. You can find it in the :doc:`Filter </channels/email/filters>` tab in the email based channels."
 msgstr ""
 
-#: ../guides/additional-customization.rst:40
-msgid "The following video shows three examples:"
-msgstr ""
-
-#: ../guides/additional-customization.rst:42
-msgid "An automatic deletion of old tickets and customers via scheduler"
-msgstr ""
-
-#: ../guides/additional-customization.rst:43
-msgid "An email rule (postmaster filter) for a specific customer"
-msgstr ""
-
-#: ../guides/additional-customization.rst:44
-msgid "A trigger to increase priority for tickets when a specific organization member is involved."
-msgstr ""
-
 #: ../guides/additional-customization.rst:50
 msgid "Add Text Modules"
 msgstr ""
@@ -6005,10 +5978,6 @@ msgstr ""
 msgid ":doc:`Text modules </manage/text-modules>` are a nice time saver for your agents. In case they answer similar questions over and over again and/or you want to unify their answers, add text modules for that. Your agents can then fetch a text by typing :kbd:`:` :kbd:`:` in the editor, followed by the name or content of the text module. You can even use variables to automatically include ticket- or customer specific text like ticket title or customer name. Just type :kbd:`:` :kbd:`:` in the text module content editor to search for available variables."
 msgstr ""
 
-#: ../guides/additional-customization.rst:61
-msgid "The video shows how to create a text module, including usage of variables and how it works for agents when dealing with a ticket."
-msgstr ""
-
 #: ../guides/additional-customization.rst:67
 msgid "Enable Checklist Feature"
 msgstr ""
@@ -6017,10 +5986,6 @@ msgstr ""
 msgid "Zammad's :doc:`checklist feature </manage/checklist>` allows you to keep track of certain tasks in a ticket. The feature allows you to create checklist templates and link to other tickets as checklist item too."
 msgstr ""
 
-#: ../guides/additional-customization.rst:73
-msgid "See how to set it up, create a template and reference to another ticket in a checklist item in the video."
-msgstr ""
-
 #: ../guides/additional-customization.rst:79
 msgid "Add AI Agents"
 msgstr ""
@@ -6041,10 +6006,6 @@ msgstr ""
 msgid "Call the AI agent in a trigger or scheduler job"
 msgstr ""
 
-#: ../guides/additional-customization.rst:89
-msgid "The video shows an example of how to set up an AI agent which rewrites the title of a ticket. A use case for this is when your customers often tend to use generic titles (like \"problem\") or you receive tickets from a web form which all have the same title."
-msgstr ""
-
 #: ../guides/additional-customization.rst:97
 msgid "Next Steps"
 msgstr ""
@@ -6122,110 +6083,102 @@ msgid "And just a note at this point so you are aware: Zammad allows you to auto
 msgstr ""
 
 #: ../guides/start-with-zammad.rst:51
-msgid "Follow the steps below for a simple setup of Zammad. You can add some information via getting started wizard or skip the steps and configure it afterwards. The guide assumes your Zammad is not yet configured. In case you see the getting started wizard, provide as much information as you desire or skip it for a later configuration. The video below shows an example with providing minimal information in the wizard."
+msgid "Follow the steps below for a simple setup of Zammad. You can add some information via getting started wizard or skip the steps and configure it afterwards."
+msgstr ""
+
+#: ../guides/start-with-zammad.rst:55
+msgid "The guide assumes your Zammad is not yet configured. In case you see the getting started wizard, provide as much information as you desire or skip it for later configuration."
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:62
+#: ../guides/start-with-zammad.rst:63
 msgid "Company Details"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:64
+#: ../guides/start-with-zammad.rst:65
 msgid "The basic customization step in Zammad is to add your company name and your logo. If not already set in the getting started wizard, visit Zammad's admin settings and go to *Settings > Branding* to adjust it. Additional information on this topic can be found in the :doc:`branding settings section </settings/branding>`."
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:71
+#: ../guides/start-with-zammad.rst:72
 msgid "Create Groups"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:73
+#: ../guides/start-with-zammad.rst:74
 msgid "A group in Zammad typically represents a department of a company. You can define which agent has access to which group and define permissions. A group can have a specific email address and department name. Use the default shipped **Users** group by renaming it. At this point, just add your groups and give them a fitting name. Create A structure in case you need it by setting parent groups. It is totally fine to stay with one group too, of course."
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:81
-msgid "You can find a video about a simple group and role configuration in the next section."
-msgstr ""
-
-#: ../guides/start-with-zammad.rst:85
+#: ../guides/start-with-zammad.rst:86
 msgid "Create or Modify Roles"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:87
+#: ../guides/start-with-zammad.rst:88
 msgid "Zammad comes with three pre-defined :doc:`roles </manage/roles/index>` for customers, agents and admins. A user can have one or more roles assigned. In a role, you can define the application permissions (what areas/features are accessible) as well as the access level to groups (read, create, change, overview, full). These three roles should cover standard scenarios. In case you wonder which additional roles could make sense, here are some examples:"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:94
+#: ../guides/start-with-zammad.rst:95
 msgid "Team leader"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:95
+#: ../guides/start-with-zammad.rst:96
 msgid "Reporting person"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:96
+#: ../guides/start-with-zammad.rst:97
 msgid "Knowledgebase editor"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:98
+#: ../guides/start-with-zammad.rst:99
 msgid "You can assign application and group permissions to a specific user as well. In case you expect more than one person with specific permissions, creating a role may be a good idea."
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:105
+#: ../guides/start-with-zammad.rst:106
 msgid "Connect Email Accounts to Zammad"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:107
+#: ../guides/start-with-zammad.rst:108
 msgid "Depending on your used email system, follow the actual guide for it:"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:109
+#: ../guides/start-with-zammad.rst:110
 msgid ":doc:`Standard IMAP/SMTP </channels/email/index>`"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:110
+#: ../guides/start-with-zammad.rst:111
 msgid ":doc:`M365 Graph </channels/microsoft365-graph/index>`"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:111
+#: ../guides/start-with-zammad.rst:112
 msgid ":doc:`M365 IMAP </channels/microsoft365/index>`"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:112
+#: ../guides/start-with-zammad.rst:113
 msgid ":doc:`Google Email </channels/google/index>`"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:114
+#: ../guides/start-with-zammad.rst:115
 msgid "After adding an email channel, create one or more signatures. You can use one signature for many groups or create different signatures, depending on your company's department structure."
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:118
-msgid "The following video shows a dummy email channel configuration as well as adding email adresses and signatures to different groups."
-msgstr ""
-
-#: ../guides/start-with-zammad.rst:121
-msgid "VIDEO HERE (created)."
-msgstr ""
-
-#: ../guides/start-with-zammad.rst:124
+#: ../guides/start-with-zammad.rst:125
 msgid "Configure Groups"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:126
+#: ../guides/start-with-zammad.rst:127
 msgid "After setting up an email based channel, a revisiting of the groups is indicated. Go to *Manage > Groups*, select each group and set an outbound email adress as well as a signature."
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:131
+#: ../guides/start-with-zammad.rst:132
 msgid "Create Agent Accounts"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:133
+#: ../guides/start-with-zammad.rst:134
 msgid "Create a :doc:`user </manage/users/index>` for each of your support agents by going to the first steps section and use the **Invite agents/colleagues to help working on tickets** function. Make sure to assign the right role to each of the agents. This step sends out invitation emails to your agents."
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:142
+#: ../guides/start-with-zammad.rst:143
 msgid "Further Steps"
 msgstr ""
 
-#: ../guides/start-with-zammad.rst:144
+#: ../guides/start-with-zammad.rst:145
 msgid "At this stage, you are ready to use Zammad in production and take advantage of the collaboration and organization features. To customize it further, follow the :doc:`additional customization guide <additional-customization>` or read on in the specific documentation sections."
 msgstr ""