to obtain the **offline license**"
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/eval-license-popup-offline.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/eval-license-popup-offline.png)
@@ -67,22 +67,22 @@ The **license token** is sent by email. The **offline license** can be retrieved
1. Open the i-doit installation in your browser. To access the [Admin Center](../administration/admin-center.md), click on the link in the login screen.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/02-update-login.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/02-update-login.png)
2. Next, enter the credentials that were set during the i-doit installation for the [Admin Center](../administration/admin-center.md).
!!! note "If you are using the **eval version**, use `admin` as the username and `admin` as the password.
If you are using the **eval appliance**, use `admin` as the username and `idoit` as the password."
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/03-update-login-admin-center.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/03-update-login-admin-center.png)
3. Click on the **Licenses** tab.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/04-update-admin-center-home.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/04-update-admin-center-home.png)
4. Paste the **license token** into the text field.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/05-update-insert-weblicense-token.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/05-update-insert-weblicense-token.png)
5. Click the {++Save & Check++} button. The **license token** is now verified by the license server and i-doit is licensed.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/06-update-save-and-check.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/06-update-save-and-check.png)
@@ -93,37 +93,37 @@ The **license token** is sent by email. The **offline license** can be retrieved
1. Log in to the [customer portal](https://center.i-doit.com/portal/advanced) and copy the **offline license** from the **Advanced** tab.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/01-update-get-offline-token.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/01-update-get-offline-token.png)
2. Open the i-doit installation in your browser. To access the [Admin Center](../administration/admin-center.md), click on the link in the login screen.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/02-update-login.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/02-update-login.png)
3. Next, enter the credentials that were set during the i-doit installation for the [Admin Center](../administration/admin-center.md).
!!! note "If you are using the **eval version**, use `admin` as the username and `admin` as the password.
If you are using the **eval appliance**, use `admin` as the username and `idoit` as the password."
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/03-update-login-admin-center.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/03-update-login-admin-center.png)
4. Click on the **Licenses** tab.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/04-update-admin-center-home.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/04-update-admin-center-home.png)
5. Paste the **license token** into the text field.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/05-update-insert-weblicense-token.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/05-update-insert-weblicense-token.png)
6. Click the {++Save++} button. Do **not** click {--Save & Check--}.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/06-update-save.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/06-update-save.png)
7. After the license token has been saved, click the **Install new license** button.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/07-update-offline-install-new-license.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/07-update-offline-install-new-license.png)
8. Here the field is displayed where the entire **offline license** must be pasted. Where to get the **offline license** is described [here](#how-do-i-obtain-the-license-token-and-the-offline-license).
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/08-update-offline-insert-offline-license.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/08-update-offline-insert-offline-license.png)
9. Then click the **Add license** button.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/09-update-offline-insert-offline-license-add-license.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/09-update-offline-insert-offline-license-add-license.png)
10. The license token is verified with the **offline license** and all associated licenses are displayed.
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/10-update-offline-done.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/10-update-offline-done.png)
@@ -147,4 +147,4 @@ To use the Add-on & Subscription Center in i-doit, some firewall rules may be re
Open the **Tenants** tab in the Admin Center. Please note that in the **Tenants** tab you can configure how many object licenses are assigned to a tenant. Even if only a single tenant exists, a disabled automatic license distribution can cause not all object licenses to be used. If this is the case, you can simply enable it and it will take effect after clicking Save.
!!! success ""
- [](../assets/images/de/wartung-und-betrieb/lizenzierung/faq-license-settings.png)
+ [](../assets/images/en/maintenance-and-operation/licensing/faq-license-settings.png)
diff --git a/docs/en/software-development/database-model/index.md b/docs/en/software-development/database-model/index.md
index b3badeae5..779d76ff8 100644
--- a/docs/en/software-development/database-model/index.md
+++ b/docs/en/software-development/database-model/index.md
@@ -91,12 +91,12 @@ Specific categories behave the same way. The query for network information of al
**Diagram: Relationship between categories and objects**
-**[](../../assets/images/de/software-entwicklung/datenbank-modell/1-dm.png)
+**[](../../assets/images/en/software-development/database-model/1-dm.png)
**
The graphic shows how an object is linked to the global category CPU. This category in turn accesses Dialog+ entries such as the manufacturer and the type. The same happens with the global category Form Factor, which accesses the form factor type.
-[](../../assets/images/de/software-entwicklung/datenbank-modell/2-dm.png)
+[](../../assets/images/en/software-development/database-model/2-dm.png)
This illustration explains the relationships of an object to the "Host Address" (IP) category. The object itself (e.g., server1) is located in the table isys\_obj. The assigned IP addresses are in the table isys\_catg\_ip\_list. Due to the detailed configuration depth of the host address, three additional tables are referenced besides the basic information (hostname, address, etc.):
diff --git a/docs/en/upgrades-and-migrations/update-guide.md b/docs/en/upgrades-and-migrations/update-guide.md
index e91d01ec8..a7611d94d 100644
--- a/docs/en/upgrades-and-migrations/update-guide.md
+++ b/docs/en/upgrades-and-migrations/update-guide.md
@@ -43,7 +43,7 @@ If prompted, overwrite everything by entering **A**.
Now open the web interface updater, select the update to v1.8 and perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/1-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/1-u18-119.png)
!!! warning "**Possible error**"
PHP Fatal error: Call to an undefined method idoit\Component\ContainerFacade::has() in /var/www/html/src/idoit/Model/Summary/SystemSummary.php on line 185
@@ -64,7 +64,7 @@ sudo -u www-data unzip idoit-1.9-update.zip
If prompted, overwrite everything by entering **A**.
Now open the web interface updater, select the update to v1.9 and perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/2-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/2-u18-119.png)
!!! success "**Check the update logs**"
Please take the time to review the logs and check whether an error has occurred.
@@ -81,7 +81,7 @@ sudo -u www-data unzip idoit-1.10-update.zip
If prompted, overwrite everything by entering **A**.
Now open the web interface updater, select the update to v1.10 and perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/3-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/3-u18-119.png)
!!! success "**Check the update logs**"
Please take the time to review the logs and check whether an error has occurred.
@@ -127,7 +127,7 @@ sudo -u www-data unzip idoit-1.12-update.zip
If prompted, overwrite everything by entering **A**.
Now open the web interface updater and the update to v1.12 is displayed and selected; perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/4-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/4-u18-119.png)
!!! success "**Check the update logs**"
Please take the time to review the logs and check whether an error has occurred.
@@ -411,7 +411,7 @@ If prompted, overwrite everything by entering **A**.
Now open the web interface updater. The update to v1.13 is displayed and selected; perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/5-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/5-u18-119.png)
You may receive this error:
@@ -437,7 +437,7 @@ If prompted, overwrite everything by entering **A**.
Now open the web interface updater. The update to v1.14 is displayed and selected; perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/6-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/6-u18-119.png)
!!! success "**Check the update logs**"
Please take the time to review the logs and check whether an error has occurred.
@@ -466,7 +466,7 @@ If prompted, overwrite everything by entering **A**.
Now open the web interface updater. The update to v1.15 is displayed and selected; perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/7-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/7-u18-119.png)
!!! success "**Check the system and i-doit**"
Check your system and i-doit!
@@ -485,7 +485,7 @@ If prompted, overwrite everything by entering **A**.
Now open the web interface updater. The update to v1.16 is displayed and selected; perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/8-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/8-u18-119.png)
!!! success "**Check the system and i-doit**"
Check your system and i-doit!
@@ -504,7 +504,7 @@ If prompted, overwrite everything by entering **A**.
Now open the web interface updater. The update to v1.17 is displayed and selected; perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/9-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/9-u18-119.png)
!!! success "**Check the system and i-doit**"
Check your system and i-doit!
@@ -521,7 +521,7 @@ If prompted, overwrite everything by entering **A**.
Now open the web interface updater. The update to v1.18 is displayed and selected; perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/10-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/10-u18-119.png)
!!! success "**Check the system and i-doit**"
Check your system and i-doit!
@@ -662,7 +662,7 @@ If you attempt the update without PHP 7.4, you will see this message:
Now open the web interface updater. The update to v1.19 is displayed and selected; perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/11-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/11-u18-119.png)
!!! success "**Check the system and i-doit**"
@@ -682,7 +682,7 @@ If prompted, overwrite everything by entering **A**.
In the web interface, verify that the update to version 20 is displayed and selected, then perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/12-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/12-u18-119.png)
!!! success "**Check the update logs**"
Please take the time to review the logs and check whether an error has occurred.
@@ -701,7 +701,7 @@ If prompted, overwrite everything by entering **A**.
In the web interface of the updater, verify that the update to version 29 is displayed and selected, then perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/13-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/13-u18-119.png)
!!! success "**Check the update logs**"
Please take the time to review the logs and check whether an error has occurred.
@@ -852,7 +852,7 @@ If prompted, overwrite everything by entering **A**.
In the web interface updater, verify that the update to version 34 is displayed and selected, then perform the update.
-[](../assets/images/de/upgrades-und-umzuege/update-anleitung-1.7.4-bis-31/14-u18-119.png)
+[](../assets/images/en/upgrades-and-migrations/update-from-1.7.4-to-1.19/14-u18-119.png)
!!! success "**Check the update logs**"
Please take the time to review the logs and check whether an error has occurred.
diff --git a/docs/en/use-cases/i-doit-patch-manager-bridge.md b/docs/en/use-cases/i-doit-patch-manager-bridge.md
index 5ea1ffdd4..6a8a494f2 100644
--- a/docs/en/use-cases/i-doit-patch-manager-bridge.md
+++ b/docs/en/use-cases/i-doit-patch-manager-bridge.md
@@ -16,37 +16,37 @@ We use the ability to automatically generate access links in i-doit to open the
1. Navigate to "Extras/Templates", click on "New Template" and create a new template with the object type "server".
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/1.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/1.png){:target="_blank"}
2. Name the template "Patch Manager bridge"
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/2.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/2.png){:target="_blank"}
3. Navigate to the "Access" category and click "New Entry"
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/3.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/3.png){:target="_blank"}
4. Name the new entry e.g. "Patch manager" and give it a custom type if you want.
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/4.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/4.png){:target="_blank"}
5. Enter the URL in the format `http(s)://mypatchmanager.server.com(:myport)/patchmanager.plp?initial-overview=%objectname|encode%`, where the variable `%objectname%` can be replaced by any of the available i-doit placeholder variables. You can get a list of available variables by clicking the info button next to the URL field.
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/5.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/5.png){:target="_blank"}
Example: `https://mypatchmanager.com:8080/patchmanager.plp?initial-overview=%objectname|encode%`
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/6.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/6.png){:target="_blank"}
!!! success "When the user later clicks the link, the Patch Manager Launcher will be opened with this parameter. The value of the URL parameter for Patch Manager can be either the device name or the value of any attribute associated with the device. Patch Manager opens the object that matches the value.
**The value must be unique** (e.g., if there are two objects named `Server12345`, the value will be skipped and the link will default to the parent location overview)."
6. Save the entry in the "Access" category
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/7.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/7.png){:target="_blank"}
7. Click on your profile icon in the top right corner and select "Administration". Then go to "Data Structure" / "Object Types" / "Infrastructure" and select "Server".
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/8.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/8.png){:target="_blank"}
8. Click "Edit" and scroll down to the "Default Template" field. Select the newly created "Patch Manager bridge" template and "Save" the settings.
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/9.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/9.png){:target="_blank"}
9. The i-doit configuration is complete. Every time a new server is created, the "Default Template" with the entry in the Access category will be applied to the object. You can now easily open "Patch Manager" via the link to switch between the tools.
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/10.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/10.png){:target="_blank"}
!!! bug "For the URL to be built correctly in i-doit, a hotfix must be applied. The hotfix can be found [HERE](../administration/hotfixes/index.md)."
@@ -63,10 +63,10 @@ These steps describe the configuration of i-doit as an external application in P
1. Go to the "Administration" / "External Applications Overview" menu.
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/11.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/11.png){:target="_blank"}
2. In the "External Applications Overview", add a new "External Application".
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/12.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/12.png){:target="_blank"}
3. Enter "i-doit" as the name, "browser" as the "Executable", and then enter the i-doit URL in the following format: `http(s)://my-i-doit.server.com(:myport)/open-object/[Label|url]`
@@ -74,11 +74,11 @@ These steps describe the configuration of i-doit as an external application in P
!!! success "Patch Manager creates a link with the object name as an entry for a third-party application. Once you click this link, the default browser opens and navigates to your i-doit instance. i-doit interprets the Patch Manager label and matches it with the object name. If it finds a unique entry, it opens the respective object.
Optionally advanced usage: The "URL-Router" also provides the following URL routes:
`/open-object-by-ip/`
`/open-object-by-inventory/`
You can use these, for example, with the Patch Manager variables `[ipaddress]` and `[inventory]` if you have created corresponding custom fields for them."
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/13.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/13.png){:target="_blank"}
4. Go to the "Application" tab and apply the application to the object type "Server" (or another object type).
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/14.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/14.png){:target="_blank"}
5. You are done with Patch Manager! To launch the link, right-click on a device and select "Launch" and then the "i-doit" submenu item.
- [](../assets/images/de/anwendungsfaelle/i-doit-patch-manager-bridge/15.png){:target="_blank"}
+ [](../assets/images/en/use-cases/i-doit-patch-manager-bridge/15.png){:target="_blank"}
diff --git a/docs/en/use-cases/ip-adress-management.md b/docs/en/use-cases/ip-adress-management.md
index b76f0440f..3f26cffc3 100644
--- a/docs/en/use-cases/ip-adress-management.md
+++ b/docs/en/use-cases/ip-adress-management.md
@@ -79,13 +79,13 @@ When assigning an IP to a network (category **Host address**), the choice of **a
Apart from CIDR, a subnet can be logically divided into multiple segments. This is useful when assigning IP addresses for specific tasks or for specific departments.
-[](../assets/images/de/anwendungsfaelle/ipam/1-ipam.png)
+[](../assets/images/en/use-cases/ipam/1-ipam.png)
Each segment is created as an object of type **Net Zone**. The category folder of the same name is available there. In the subordinate category **Options**, a **zone color** can be selected. This color is used in the **Net > IP List** category. Furthermore, the sub-category **Zones** displays the address ranges of the assigned subnets of type **Layer 3 Net**.
The assignment of a zone to a subnet takes place in the **Net > IP List** category of a subnet: First, you select an IP address or a range of IP addresses. Then you assign the segment to these IP addresses via the **New zone** button. The IP addresses are marked in the color of the zone.
-[](../assets/images/de/anwendungsfaelle/ipam/2-ipam.png)
+[](../assets/images/en/use-cases/ipam/2-ipam.png)
In the **Host address** category, the next free IP address is automatically suggested based on the selected net zone. The **Domain** attribute in the **Net Zone > Options** category additionally ensures that when new IP addresses are assigned in the **Host address** category, this domain is automatically preselected.
@@ -93,7 +93,7 @@ In the **Host address** category, the next free IP address is automatically sugg
If you want to maintain information about the Domain Name System (DNS) and/or Fully Qualified Domain Names (FQDNs) used, you can do so with i-doit. For each **Layer 3 Net**, any number of **DNS servers** (object relationship) and domains can be stored in the **Net** category. Deviating settings for DNS servers and domains used can be stored per object in the **Host address** category. If an object receives one or more hostnames (category **Host address**) and information about the domains used, one or more FQDNs are derived, which are displayed automatically. Domains can be inherited through the assignment to a network. Additionally, **search domains** can be specified.
-[](../assets/images/de/anwendungsfaelle/ipam/3-ipam.png)
+[](../assets/images/en/use-cases/ipam/3-ipam.png)
!!! info "Configuration data for DNS and DHCP servers"
In principle, the documented data is suitable for supplying DNS or DHCP servers with matching configuration data. i-doit includes an [export function for the ISC DHCP DNS server](../automation-and-integration/cli/index.md).
diff --git a/docs/en/use-cases/switch-stacking.md b/docs/en/use-cases/switch-stacking.md
index 244ad40a2..c9b13e570 100644
--- a/docs/en/use-cases/switch-stacking.md
+++ b/docs/en/use-cases/switch-stacking.md
@@ -14,17 +14,17 @@ Stack Members
In the **Stack Members** category created for stacking, [objects](../glossary.md) can be added as members of the stack and marked as "Active" or "Passive". In the documentation, this marking has no further effect other than the corresponding display.
-[](../assets/images/de/anwendungsfaelle/switch-stacking/1-sws.png)
+[](../assets/images/en/use-cases/switch-stacking/1-sws.png)
-[](../assets/images/de/anwendungsfaelle/switch-stacking/2-sws.png)
+[](../assets/images/en/use-cases/switch-stacking/2-sws.png)
Logical Ports
--------------
When a logical port is created in one of the stack members, it now also appears in the other stack members under logical ports.
-[](../assets/images/de/anwendungsfaelle/switch-stacking/3-sws.png)
+[](../assets/images/en/use-cases/switch-stacking/3-sws.png)
Additionally, the logical port of another stack member can be assigned as the parent port of a port.
-[](../assets/images/de/anwendungsfaelle/switch-stacking/4-sws.png)
+[](../assets/images/en/use-cases/switch-stacking/4-sws.png)
diff --git a/docs/en/use-cases/variable-reports.md b/docs/en/use-cases/variable-reports.md
index e6fad3a14..346c135e1 100644
--- a/docs/en/use-cases/variable-reports.md
+++ b/docs/en/use-cases/variable-reports.md
@@ -21,19 +21,19 @@ To trace which printer is assigned to which room from both the room and the prin
To assign printers to the respective rooms, we create a custom category called **Area Printer**.
This is assigned to the [object type](../basics/it-documentation-structure.md#objekttyp) **Printer** and defined as a [single-value category](../basics/it-documentation-structure.md#single-value-kategorie). The [attribute](../basics/it-documentation-structure.md#attribut) **Area printer for** is added as an **Object relationship (Multiple objects)** with the addition **Share access**.
-[](../assets/images/de/anwendungsfaelle/variable-reports/1-vr.png)
+[](../assets/images/en/use-cases/variable-reports/1-vr.png)
Then switch to the object **HQ Staff Printer 01**. In the **Area Printer** category, select the assigned rooms.
-[](../assets/images/de/anwendungsfaelle/variable-reports/2-vr.png)
+[](../assets/images/en/use-cases/variable-reports/2-vr.png)
The result in the category looks like the following image.
-[](../assets/images/de/anwendungsfaelle/variable-reports/3-vr.png)
+[](../assets/images/en/use-cases/variable-reports/3-vr.png)
This can also be visualized with the [CMDB Explorer](../evaluation/cmdb-explorer/index.md).
-[](../assets/images/de/anwendungsfaelle/variable-reports/4-vr.png)
+[](../assets/images/en/use-cases/variable-reports/4-vr.png)
So far so good. But how do you find out, when looking at room **1.05**, which area printer is defined for this room? A reverse view is needed to determine which printer is related to this room. Variable reports provide a solution for such context-dependent queries.
@@ -43,16 +43,16 @@ In the query editor, there is the option to set a **field placeholder** under **
For this use case, this means: The report "searches" for those objects where, in the custom category **Area Printer** in the attribute **Area printer for**, the [object ID](../basics/unique-references.md) of the currently selected object is entered. But what is the selected object? In the context of the Report Manager, there is no selected object. This turns the report into a variable report.
-[](../assets/images/de/anwendungsfaelle/variable-reports/5-vr.png)
+[](../assets/images/en/use-cases/variable-reports/5-vr.png)
Therefore, an object must always be selected to fill the report. In this case, this is done by creating a category for the report that executes the report within an object. This is called **Area Printer Reverse** and is assigned to the **Room** object type as a single-value category. It receives a nameless attribute with the **field type Report**. Under **Addition**, you can then select the name of the report created above.
-[](../assets/images/de/anwendungsfaelle/variable-reports/6-vr.png)
+[](../assets/images/en/use-cases/variable-reports/6-vr.png)
The report ID is included in the overview of already defined reports.
-[](../assets/images/de/anwendungsfaelle/variable-reports/7-vr.png)
+[](../assets/images/en/use-cases/variable-reports/7-vr.png)
In room objects, the new category is now available, which always executes the report for the object the user is currently in. This provides a reverse view of the relationship to the area printer.
-[](../assets/images/de/anwendungsfaelle/variable-reports/8-vr.png)
+[](../assets/images/en/use-cases/variable-reports/8-vr.png)
diff --git a/docs/en/user-authentication-and-management/ldap-directory/i-doit-win-ldaps.md b/docs/en/user-authentication-and-management/ldap-directory/i-doit-win-ldaps.md
index dedfcdf49..fa9e33c82 100644
--- a/docs/en/user-authentication-and-management/ldap-directory/i-doit-win-ldaps.md
+++ b/docs/en/user-authentication-and-management/ldap-directory/i-doit-win-ldaps.md
@@ -39,4 +39,4 @@ Then restart Apache2 HTTPD via the command prompt: `C:\i-doit\apache-2.4\bin\htt
Log in to i-doit and create a new server entry under **Administration > Import and Interfaces > LDAP > Server**. Fill in all required fields and set **TLS** to **LDAPS**.
-[](../../assets/images/de/benutzerauthentifizierung-und-verwaltung/ldap-verzeichnis/i-doit-win-ldaps/i-doit-conf.png)
+[](../../assets/images/en/user-authentication-and-management/ldap-directory/i-doit-win-ldaps/i-doit-conf.png)
diff --git a/docs/en/user-authentication-and-management/ldap-directory/index.md b/docs/en/user-authentication-and-management/ldap-directory/index.md
index cca93c036..5e362d122 100644
--- a/docs/en/user-authentication-and-management/ldap-directory/index.md
+++ b/docs/en/user-authentication-and-management/ldap-directory/index.md
@@ -177,7 +177,7 @@ To set up the assignment:
During login or synchronization, i-doit compares the user's group memberships in the directory with the configured mappings. If they match, the person group is automatically assigned.
-[](../../assets/images/de/automatisierung-und-integration/ldap/1-ldap.png)
+[](../../assets/images/en/automation-and-integration/ldap/1-ldap.png)
!!! info "memberOf with OpenLDAP"
The automatic assignment relies on the LDAP query that determines which groups a user belongs to. The memberOf attribute plays an important role here. This attribute must be available as an overlay, which is not the case in many default installations of OpenLDAP. Good articles on the required configuration can be found [here](http://www.adimian.com/blog/2014/10/how-to-enable-memberof-using-openldap/) and [here](https://technicalnotes.wordpress.com/2014/04/19/openldap-setup-with-memberof-overlay/).
@@ -190,7 +190,7 @@ A detailed guide can be found in the article [Import users and groups from AD/LD
The executing user requires supervisor permissions on the categories **Group membership** and **Person groups > Members** as well as on the object types **Persons** and **Person groups**.
-[](../../assets/images/de/automatisierung-und-integration/ldap/2-ldap.png)
+[](../../assets/images/en/automation-and-integration/ldap/2-ldap.png)
## Logging
diff --git a/docs/en/user-authentication-and-management/ldap-directory/ldap-tls.md b/docs/en/user-authentication-and-management/ldap-directory/ldap-tls.md
index 43c370a80..f60730282 100644
--- a/docs/en/user-authentication-and-management/ldap-directory/ldap-tls.md
+++ b/docs/en/user-authentication-and-management/ldap-directory/ldap-tls.md
@@ -13,27 +13,27 @@ This guide shows you how to set up an encrypted LDAPS or STARTTLS connection bet
Log in to the LDAP server, which typically also contains the certificate authority. Open the corresponding MMC snap-in or select the **Certificate Authority** option in Server Manager.
-[](../../assets/images/de/automatisierung-und-integration/ldap/ldap-tls/ldap-tls-1.png)
+[](../../assets/images/en/automation-and-integration/ldap/ldap-tls/ldap-tls-1.png)
Select the properties of the certificate authority.
-[](../../assets/images/de/automatisierung-und-integration/ldap/ldap-tls/ldap-tls-2.png)
+[](../../assets/images/en/automation-and-integration/ldap/ldap-tls/ldap-tls-2.png)
Display the certificate (1), select **Details** (2), and then copy it to a file (3).
-[](../../assets/images/de/automatisierung-und-integration/ldap/ldap-tls/ldap-tls-3.png)
+[](../../assets/images/en/automation-and-integration/ldap/ldap-tls/ldap-tls-3.png)
Keep the DER format selected.
-[](../../assets/images/de/automatisierung-und-integration/ldap/ldap-tls/ldap-tls-4.png)
+[](../../assets/images/en/automation-and-integration/ldap/ldap-tls/ldap-tls-4.png)
Choose a file name and directory.
-[](../../assets/images/de/automatisierung-und-integration/ldap/ldap-tls/ldap-tls-5.png)
+[](../../assets/images/en/automation-and-integration/ldap/ldap-tls/ldap-tls-5.png)
Complete the export wizard.
-[](../../assets/images/de/automatisierung-und-integration/ldap/ldap-tls/ldap-tls-6.png)
+[](../../assets/images/en/automation-and-integration/ldap/ldap-tls/ldap-tls-6.png)
## Step 2: Set Up Certificate on the i-doit Server
diff --git a/docs/en/user-authentication-and-management/sso-comparison/saml/adfs-saml.md b/docs/en/user-authentication-and-management/sso-comparison/saml/adfs-saml.md
index 8d0615a32..3f6f2dc8f 100644
--- a/docs/en/user-authentication-and-management/sso-comparison/saml/adfs-saml.md
+++ b/docs/en/user-authentication-and-management/sso-comparison/saml/adfs-saml.md
@@ -184,63 +184,63 @@ The configuration of the Linux server is now complete for the time being. In the
First download the `mellon_metadata.xml` from the Linux server (e.g. via WinSCP). Then open the AD FS Management and create a new Relying Party Trust:
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-1.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-1.png)
Leave **Claims aware** active and click **Start**.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-2.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-2.png)
In the next step, select **Import data from a file** and navigate to the previously saved XML file.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-3.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-3.png)
The following notice can be ignored if it appears.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-4.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-4.png)
Enter the FQDN of your Linux server.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-5.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-5.png)
In the next step you can configure access control. To start, leave the setting at **Permit everyone**.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-6.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-6.png)
You can skip the next window -- click **Next**.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-7.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-7.png)
Click **Close** -- the Relying Party Trust is now created.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-8.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-8.png)
Now define the **Claim Issuance Policies** so that users can log in via email.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-9.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-9.png)
A window opens -- click **Add Rule**.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-10.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-10.png)
Select **Send LDAP Attributes as Claim** and click **Next**.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-11.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-11.png)
Give the rule a unique name and add the mapping as shown.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-12.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-12.png)
Create an additional rule and select **Transform an Incoming Claim**.
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-13.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-13.png)
Apply the configuration as follows:
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-14.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-14.png)
The Relying Party Trust is now fully configured. Test the authentication:
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-15.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-15.png)
## Test SAML-SSO
@@ -249,7 +249,7 @@ Open the URL of the server in your browser:
After successful login you should see the following output:
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-16.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-16.png)
## Install i-doit
@@ -263,7 +263,7 @@ Open the **System settings** tab in the [Admin Center](../../../administration/a
The email address of the respective user must be stored as the login in i-doit!
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-17.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-17.png)
Adjust the VHost configuration so that SSO login works.
diff --git a/docs/en/user-authentication-and-management/sso-comparison/saml/azure-ad-saml.md b/docs/en/user-authentication-and-management/sso-comparison/saml/azure-ad-saml.md
index d90332a70..faa8ad5ba 100644
--- a/docs/en/user-authentication-and-management/sso-comparison/saml/azure-ad-saml.md
+++ b/docs/en/user-authentication-and-management/sso-comparison/saml/azure-ad-saml.md
@@ -134,7 +134,7 @@ Open the **System settings** tab in the [Admin Center](../../../administration/a
The email address of the respective user must be stored as the login in i-doit!
-[](../../../assets/images/de/benutzerauthentifizierung-und-verwaltung/sso-vergleich/saml/adfs-saml/saml-17.png)
+[](../../../assets/images/en/user-authentication-and-management/sso-comparison/saml/adfs-saml/saml-17.png)
As long as the configurations on the Linux server have not been enabled yet, users can still log in with the i-doit login form and a local user.
diff --git a/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/1-nag.png b/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/1-nag.png
index f8bb7725e..947f8e86d 100644
Binary files a/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/1-nag.png and b/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/1-nag.png differ
diff --git a/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/3-nag.png b/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/3-nag.png
index 29303dbfa..a77b4db1f 100644
Binary files a/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/3-nag.png and b/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/3-nag.png differ
diff --git a/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/4-nag.png b/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/4-nag.png
index f8bb7725e..947f8e86d 100644
Binary files a/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/4-nag.png and b/overrides/assets/images/en/automation-and-integration/network-monitoring/nagios/4-nag.png differ
diff --git a/overrides/assets/images/en/automation-and-integration/service-desk/3-sd.png b/overrides/assets/images/en/automation-and-integration/service-desk/3-sd.png
new file mode 100644
index 000000000..2680b4343
Binary files /dev/null and b/overrides/assets/images/en/automation-and-integration/service-desk/3-sd.png differ
diff --git a/overrides/assets/images/en/automation-and-integration/snmp/2-snmp.png b/overrides/assets/images/en/automation-and-integration/snmp/2-snmp.png
new file mode 100644
index 000000000..6eee64884
Binary files /dev/null and b/overrides/assets/images/en/automation-and-integration/snmp/2-snmp.png differ
diff --git a/overrides/assets/images/en/automation-and-integration/snmp/3-snmp.png b/overrides/assets/images/en/automation-and-integration/snmp/3-snmp.png
new file mode 100644
index 000000000..6cd59f8f6
Binary files /dev/null and b/overrides/assets/images/en/automation-and-integration/snmp/3-snmp.png differ
diff --git a/overrides/assets/images/en/basics/attribute-fields/hinzufuegen.png b/overrides/assets/images/en/basics/attribute-fields/hinzufuegen.png
new file mode 100644
index 000000000..6044f17ce
Binary files /dev/null and b/overrides/assets/images/en/basics/attribute-fields/hinzufuegen.png differ
diff --git a/overrides/assets/images/en/basics/object-list/2-ol.gif b/overrides/assets/images/en/basics/object-list/2-ol.gif
new file mode 100644
index 000000000..c58a6cf9a
Binary files /dev/null and b/overrides/assets/images/en/basics/object-list/2-ol.gif differ
diff --git a/overrides/assets/images/en/basics/object-list/3-ol.gif b/overrides/assets/images/en/basics/object-list/3-ol.gif
new file mode 100644
index 000000000..4634828cc
Binary files /dev/null and b/overrides/assets/images/en/basics/object-list/3-ol.gif differ
diff --git a/overrides/assets/images/en/basics/object-list/advanced-settings.png b/overrides/assets/images/en/basics/object-list/advanced-settings.png
new file mode 100644
index 000000000..262935a41
Binary files /dev/null and b/overrides/assets/images/en/basics/object-list/advanced-settings.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/1-web-gui.png b/overrides/assets/images/en/basics/web-gui/1-web-gui.png
new file mode 100644
index 000000000..8f2acb05f
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/1-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/10-web-gui.png b/overrides/assets/images/en/basics/web-gui/10-web-gui.png
new file mode 100644
index 000000000..aea044e60
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/10-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/11-web-gui.png b/overrides/assets/images/en/basics/web-gui/11-web-gui.png
new file mode 100644
index 000000000..6c3a93c62
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/11-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/12-web-gui.png b/overrides/assets/images/en/basics/web-gui/12-web-gui.png
new file mode 100644
index 000000000..c282f0c45
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/12-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/13-web-gui.png b/overrides/assets/images/en/basics/web-gui/13-web-gui.png
new file mode 100644
index 000000000..147b6ec98
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/13-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/2-web-gui.png b/overrides/assets/images/en/basics/web-gui/2-web-gui.png
new file mode 100644
index 000000000..c03812e59
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/2-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/3-web-gui.png b/overrides/assets/images/en/basics/web-gui/3-web-gui.png
new file mode 100644
index 000000000..2f77945da
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/3-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/4-web-gui.png b/overrides/assets/images/en/basics/web-gui/4-web-gui.png
new file mode 100644
index 000000000..ca1f75875
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/4-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/5-web-gui.png b/overrides/assets/images/en/basics/web-gui/5-web-gui.png
new file mode 100644
index 000000000..f085e785a
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/5-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/6-web-gui.png b/overrides/assets/images/en/basics/web-gui/6-web-gui.png
new file mode 100644
index 000000000..b21d7e8e1
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/6-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/7-web-gui.png b/overrides/assets/images/en/basics/web-gui/7-web-gui.png
new file mode 100644
index 000000000..be7070b41
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/7-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/8-web-gui.png b/overrides/assets/images/en/basics/web-gui/8-web-gui.png
new file mode 100644
index 000000000..40526e093
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/8-web-gui.png differ
diff --git a/overrides/assets/images/en/basics/web-gui/9-web-gui.png b/overrides/assets/images/en/basics/web-gui/9-web-gui.png
new file mode 100644
index 000000000..3cb46b6ff
Binary files /dev/null and b/overrides/assets/images/en/basics/web-gui/9-web-gui.png differ
diff --git a/overrides/assets/images/en/evaluation/cmdb-explorer/5-ce.png b/overrides/assets/images/en/evaluation/cmdb-explorer/5-ce.png
new file mode 100644
index 000000000..59f1121b6
Binary files /dev/null and b/overrides/assets/images/en/evaluation/cmdb-explorer/5-ce.png differ
diff --git a/overrides/assets/images/en/evaluation/report-manager/14-rm.png b/overrides/assets/images/en/evaluation/report-manager/14-rm.png
index acfccbe05..2365f1395 100644
Binary files a/overrides/assets/images/en/evaluation/report-manager/14-rm.png and b/overrides/assets/images/en/evaluation/report-manager/14-rm.png differ
diff --git a/overrides/assets/images/en/i-doit-add-ons/api/endpunkt-doku.png b/overrides/assets/images/en/i-doit-add-ons/api/endpunkt-doku.png
new file mode 100644
index 000000000..1fb222557
Binary files /dev/null and b/overrides/assets/images/en/i-doit-add-ons/api/endpunkt-doku.png differ
diff --git a/overrides/assets/images/en/i-doit-add-ons/maintenance/11-main.png b/overrides/assets/images/en/i-doit-add-ons/maintenance/11-main.png
new file mode 100644
index 000000000..6fba30705
Binary files /dev/null and b/overrides/assets/images/en/i-doit-add-ons/maintenance/11-main.png differ
diff --git a/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/schutzbedarf-anzeigen.png b/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/schutzbedarf-anzeigen.png
new file mode 100644
index 000000000..da6bab2ff
Binary files /dev/null and b/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/schutzbedarf-anzeigen.png differ
diff --git a/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/schutzbedarf-editieren.png b/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/schutzbedarf-editieren.png
new file mode 100644
index 000000000..9b207ba57
Binary files /dev/null and b/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/schutzbedarf-editieren.png differ
diff --git a/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/zielobjekte.png b/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/zielobjekte.png
new file mode 100644
index 000000000..c94a73104
Binary files /dev/null and b/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/zielobjekte.png differ
diff --git a/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/zielobjektgruppen.png b/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/zielobjektgruppen.png
new file mode 100644
index 000000000..de1e8bd52
Binary files /dev/null and b/overrides/assets/images/en/i-doit-add-ons/viva2/assessment-of-protection/zielobjektgruppen.png differ
diff --git a/overrides/assets/images/en/use-cases/switch-stacking/2-sws.png b/overrides/assets/images/en/use-cases/switch-stacking/2-sws.png
new file mode 100644
index 000000000..9b04b693f
Binary files /dev/null and b/overrides/assets/images/en/use-cases/switch-stacking/2-sws.png differ
diff --git a/overrides/assets/images/en/use-cases/switch-stacking/3-sws.png b/overrides/assets/images/en/use-cases/switch-stacking/3-sws.png
new file mode 100644
index 000000000..e80cd5f29
Binary files /dev/null and b/overrides/assets/images/en/use-cases/switch-stacking/3-sws.png differ
diff --git a/overrides/assets/images/en/use-cases/switch-stacking/4-sws.png b/overrides/assets/images/en/use-cases/switch-stacking/4-sws.png
new file mode 100644
index 000000000..a00849f29
Binary files /dev/null and b/overrides/assets/images/en/use-cases/switch-stacking/4-sws.png differ